Skip to content
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.

Sign up for GitHub

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

Doc/adding tst to docs #491

Merged
merged 1 commit into from
Nov 28, 2023
Merged

Doc/adding tst to docs #491

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/development/style_guide.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,7 @@ So here are a couple of **guidelines** to help you when creating new branches to
#. ``enh``: when you add new features and enhancements
#. ``maint``: when your branch is all about refactoring, fixing typos, etc.
#. ``rel``: when your branch makes changes related to creating new releases
#. ``tst``: when your branch makes changes related to tests

* Use ``-`` instead of spaces for the description text.
* Keep branch names with lowercase letters.
Expand All @@ -80,6 +81,7 @@ Here are a couple of example branch names:
- ``bug/issue-98-upside-down-rockets``
- ``enh/hybrid-motor-feature``
- ``maint/typos-flight-class``
- ``tst/refactor-tests-flight-class``

Once you are ready to create a Pull Request for your branch, we advise you to merge with the ``develop`` branch instead of the default ``master`` branch.
This way, we keep the ``master`` branch stable and use the ``develop`` branch to test out new features!
Expand Down
Loading