You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+2-14Lines changed: 2 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Feel free to propose a new feature by [opening an issue for it](https://github.c
37
37
38
38
1. Fork the repository.
39
39
1. Create a new branch.
40
-
1. If you are **implementing new functionality**, create your branch from `development`.
40
+
1. If you are **implementing new functionality**, create your branch from `main`.
41
41
1. If you are **fixing a bug**, create your branch from the oldest [supported](https://github.com/neo4j-php/php-cypher-dsl/blob/main/LIFECYCLE.md) branch that is affected by the bug.
42
42
1. Implement your change and add tests for it.
43
43
1. Make sure the test suite passes.
@@ -50,18 +50,6 @@ Some things to keep in mind:
50
50
* Keep backwards compatibility breaks to a minimum.
51
51
* You are encouraged to [sign your commits](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) with GPG.
52
52
53
-
## Branching model
54
-
55
-
The branching model used by this project is [gitflow](https://nvie.com/posts/a-successful-git-branching-model/), with the following changes/additions:
56
-
57
-
1. Feature branches must follow the naming convention `feature/*`.
58
-
1. The name of a feature branch should reflect the feature added (e.g. `feature/support-indexing-operator` instead of `feature/feature-1`).
59
-
1. Release branches must follow the naming convention `release/x.y`, where `x` and `y` are the major and minor version of the release respectively. A release branch should never be made for a patch.
60
-
1. Hotfix branches must follow the naming convention `hotfix/x.y.z`, where `x`, `y` and `z` are the major, minor and patch version of the hot respectively.
61
-
1. Hotfix branches must branch off from the oldest [supported](https://github.com/neo4j-php/php-cypher-dsl/blob/main/LIFECYCLE.md) branch that is affected by the bug.
62
-
1. Right before a new **major** version is released, a *support* branch is created from `main`.
63
-
1. Support branches must follow the naming convention `support/x.y`, where `x` and `y` are the major and minor version of the most recent release respectively.
64
-
65
53
## Coding guidelines
66
54
67
55
This project comes with a [configuration file](https://github.com/neo4j-php/php-cypher-dsl/blob/main/.php-cs-fixer.dist.php) for `php-cs-fixer` that you can use to format your code:
@@ -81,7 +69,7 @@ After making your changes and adding your tests, you can check whether the minim
81
69
```
82
70
$ XDEBUG_MODE=coverage php vendor/bin/phpunit --testsuite unit
0 commit comments