-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documenting our new code review process #9
Comments
I love the idea but pushing to branch may affect the updates for servers. |
@windhamwong I have added you as a developer to the project, however I'd still ask that you use the same process as everyone else and submit pull requests to be approved by another developer. I understand that twRO might not have very many active developers to test, but someone else should at least read your changes before they're merged into master. In the past we've run into situations where a "fix" on one server will break support on others. The review process is intended to prevent that or at least catch it before it gets pushed out to non-developer users. Things might change in the future when the project has more automated tests in place, but for now please don't push things without talking to anyone else first. ps: If you ever need to get in touch, the #OpenKore IRC channel on freenode has been pretty active lately. |
nice. I will join irc later today. |
Redirected "Current Development" link to pull requests http://openkore.com/index.php?title=Template:Index/MainLinks&curid=963&diff=3698&oldid=3687 |
@allanon and I have been discussing changes we'd like to see in regards to the way that code is submitted into the project. When we were using SVN, anyone with commit access would write code and push it up whenever they felt like it. There was rarely any communication between developers before changes were made or even testing done on different platforms / servers.
We'd like to make the entire development process more reliable and transparent by utilizing pull requests here on GitHub. So far we've already started using it amongst ourselves, but official documentation should be written to replace the old SVN guides like these:
http://wiki.openkore.com/index.php/Patches_Welcome
http://wiki.openkore.com/index.php/Development_Conventions
tldr; Don't push to master. Make a pull request and have it approved by another developer first.
The text was updated successfully, but these errors were encountered: