Branch naming
We are using a custom version of GitFlow methodology for naming the branches:
- feature:
feature/* - hotfix:
hotfix/* - documentation:
doc/* - asset:
asset/* - bug:
bug/*
Moreover, the names of the branches have to be meaningful.
Have you found a bug?
- Verify that the bug has not been reported yet by searching on Issues.
- If it does not exist, then open a new issue.
Have you fixed a bug?
- Open a pull request.
- Make sure that you describe the problem and your solution.
- Include all related issue numbers if applicable.
Do you want to add a new feature or change an existing one?
- Verify that the feature or change is not implemented yet by another user by searching on Issues.
- Send an email to appaxer@gmail.com and describe the feature or the change.
- If it is approved, then open a new issue.
- Open a feature branch and perform there all the changes you want.
- When you have finished, open a pull request.
- Make sure that you describe the new feature or the changes you have performed.
- Include the related issue number.
Have you found anything wrong in the documentation?
- Verify that the documentation issue has not been reported yet by searching on Issues.
- If it does not exist, then open a new issue.
Do you have any question?
- Verify that your question has not been asked yet by searching on Q&A.
- If it does not exist, then open a new Q&A discussion.
We follow the standard Kotlin code coventions.