Once the development branch has been tested by QA, it will be merged with the stable branch to become the next revision for the live realms. To ensure the QA team receives ample opportunity to test each set of changes, the development branch will only accept pull requests for one week before being frozen for a week, during which time only essential fixes will be accepted. The development branch is used as the basis for the QA and PTR realms. Squashing your commits is to ensure that the development branch can be compiled at any point in its history as well as ensuring a clean history. After receiving feedback and making any requested changes, your pull request will be squashed and merged to the development branch. When you have finished working on your fix or feature, you should open a pull request to allow for your code to be automatically compiled by the continuous integration system and reviewed by other developers. For example, if you were working on a boss script, rather than committing directly to the development branch, you should first create a new branch with a descriptive name. Development process overview:Īny development work should be done in local feature branches rather than on the main branches used for QA/live builds. Before opening any bug reports on the issue tracker, please read the guidelines located here.
0 Comments
Leave a Reply. |