Game Development Reference
In-Depth Information
Extra credit, push it back to Unity
So you have been going through the UI source and found a bug that you know how
to fix or have some award-winning idea that you have implemented that you think
is good enough to go into the main build, then thanks to the magic of a DCVS source
control system, we have a way.
Note: The following pattern is meant only for submitting new features or
fixed bugs. If you find something that is breaking or you don't know how
to fix it, then use the standard Unity bug reporter (
Help
|
Report a bug
)
to submit it. Don't submit a change with some notes saying it's broken
because it will likely not be picked up by anyone.
Now to submit fixes or new features, you need to keep a few things in mind if you
want it to be accepted (this is true for any open source project):
•
Keep it small
: Do this as large submissions will likely be ignored.
•
Keep it succinct
: Stay on target and fix one thing or add one feature at a time.
•
Document where possible
: This will help moderators who read the code
understand it quicker and easier.
•
Plan ahead
: If you have a number of changes, either ensure they don't
overlap/depend on each other or work with the moderators to ensure they
are aware of what's coming. There is nothing worse than having a whole
plan of work not accepted because it was too much or not what was wanted.
In the road to submission, we start from grass roots, which means you start planning
for the change before you even start coding. The basic workflow is like this:
1.
Create a new branch and keep the name simple and about your change.
2.
Add your changes in one go or in a few commits/check-ins (too many
commits in a request are bad).
Commits are when you are done making changes, then you use your
source control tool to mark a checkpoint in your coding and then push/
upload them to the server.
