For more information see GitHub Flow
GitHub Flow is very lightweight (especially compared to GitFlow). This workflow uses only two kinds of branches:
- Feature branch
- Main branch (previously called master)
The feature branches are used to develop new features as well as fixes. These branches are usually created out of main.
Anything in the main branch is deployable. The main branch is expected to be deployed regularly and is considered stable.
For more information see GitHub Flow
TL;DR
- anything in the main branch is deployable
- create descriptive branches off of main
- push to named branches constantly
- open a pull request at any time
- merge only after pull request review
- deploy immediately after review
Our current continuous integration workflow makes it very hard to work on own forks of the secureCodeBox because CI tests cannot be executed outside of our repository. We are aware of that problem and are working on a solution.
Generally the secureCodeBox project follows the standard GitHub Pull request process.
It is mandatory to open an issue, if the task takes longer than one hour. Before you open an issue please verify there is no existing one covering your issue.
For more information see here.
TL;DR
- Separate subject from body with a blank line
- Limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how
NOTE: Make sure you don't include @mentions or fixes keywords in your git commit messages. These should be included in the PR body instead.
Please have a look at our Code of Conduct before you write an Issue or make a PR.