This repository has been archived by the owner on Jun 24, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Patch release (1.0.3) of Poly Toolkit.
- Loading branch information
Showing
13 changed files
with
161 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
// Copyright 2017 Google Inc. All rights reserved. | ||
// | ||
// Licensed under the Apache License, Version 2.0 (the "License"); | ||
// you may not use this file except in compliance with the License. | ||
// You may obtain a copy of the License at | ||
// | ||
// https://www.apache.org/licenses/LICENSE-2.0 | ||
// | ||
// Unless required by applicable law or agreed to in writing, software | ||
// distributed under the License is distributed on an "AS IS" BASIS, | ||
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
// See the License for the specific language governing permissions and | ||
// limitations under the License. | ||
|
||
using System.IO; | ||
using UnityEditor; | ||
using UnityEngine; | ||
|
||
// PolyToolkitDev namespace is for classes that exist only for developing Poly Toolkit itself, | ||
// and don't ship out to users in the build. | ||
namespace PolyToolkitDev { | ||
|
||
static class PrepForUASExport { | ||
[MenuItem("Poly/Dev/Prep for UAS Export")] | ||
public static void DoPrepForUASExport() { | ||
// The exported package should have the placeholder credentials, not our credentials. | ||
BuildPackage.ResetToPlaceholderCredentials(); | ||
|
||
// We used to create upgrade.dat in the editor, so there might be left over copies of it in people's | ||
// working copies. To ensure that it's not exported, let's delete it. | ||
File.Delete(Application.dataPath + "/Editor/upgrade.dat"); | ||
File.Delete(Application.dataPath + "/Editor/upgrade.dat.meta"); | ||
|
||
EditorUtility.DisplayDialog("Ready", "Ready for Unity Asset Store export.", "OK"); | ||
} | ||
} | ||
|
||
} |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
89454b9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be lots of separate commits squashed together plus a not very descriptive commit message. Seems a bit of a shame as this negates half the benefit of having a public Git repo. I assume you've got more granular commits internally?
89454b9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, this is a series of internal commits squashed together, and we do have more granular commits internally. We do this mainly because we want to always have a stable snapshot of the source code in Github so that developers don't have to worry about the code being in an inconsistent state in between commits. Sometimes we fix one thing and break something else temporarily, then fix the other thing and break a third thing, then fix that... and so on and so forth :) So to minimize pain to external devs, we prefer to push "known good snapshots" reflecting good states of the code, as individual commits might or might not be good patches.
But maybe I'm fundamentally misunderstanding something! What's a use case in which individual commits would be vastly more useful than snapshots?
89454b9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to use commit history for two main things:
And to give a more fuzzy reason - I guess I'm just used to seeing proper commits as it's how the majority of open source projects operate. I use the Github network view a lot to keep my eye on how a project is progressing: https://github.com/thestonefox/VRTK/network
89454b9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it! Making a more detailed changelog is feasible, I'll look into improving this process. Thanks for the feedback!