Use git-rebase to keep your branch up-to-date. No merge commits inside pull requests.If you forget initially, it's okay to force push to your own fork to fix it. Please squash commits that belong together.If the commit doesn't include any changes that need CI testing (code or build system changes should always be CI tested, other things not), yet another empty line, followed by a line containing.See for a more detailed description of this feature. If the commit fixes an issue reported on GitHub, please add another empty line, followed by a line containing Closes #xyz, where #xyz is the issue to close.Detailed explanatory text for the change which can include multiple paragraphs, or bullet points.An empty line, separating message subject and body.First line: Short summary, up to 72 characters.Commit messages should follow this style:.Pull requests importing translation updates from Transifex are, unless requested by a contributor, not very welcome.
#SUPERTUX 2 FORK CODE#
Easily sync your projects with Travis CI and youll be testing your code in minutes. If the pull request is untested or work-in-progress, please mention that. Travis CI enables your team to test and ship your apps with confidence.