oppi.li
+7
CONTRIBUTING.md
+7
CONTRIBUTING.md
···
31
31
- If the PR is a new feature, it has to come with a suite of unit tests, that tests the new functionality.
32
32
- In any case, all the PRs have to pass the personal evaluation of at least one of the maintainers of go-git.
33
33
34
+
### Branches
35
+
36
+
The `master` branch is currently used for maintaining the `v5` major release only. The accepted changes would
37
+
be dependency bumps, bug fixes and small changes that aren't needed for `v6`. New development should target the
38
+
`v6-exp` branch, and if agreed with at least one go-git maintainer, it can be back ported to `v5` by creating
39
+
a new PR that targets `master`.
40
+
34
41
### Format of the commit message
35
42
36
43
Every commit message should describe what was changed, under which context and, if applicable, the GitHub issue it relates to: