-
This rules should permit a unified workflow about all our repos.
It should normalize:
* The relationship between Tickets and PRs
* The relationship between PRs and git branches
* The process of …
-
@brubash I am going to take notes here using a task list to determine what next steps are needed after the 1:00 phone call.
Code developer dependencies
- [x] Team needs to use Gitflow workflow…
-
This is obviously dead. There's a good fork available. Please close this project and tell people to use the one that's maintained. Leaving this up here isn't helping anybody.
See #6370
-
I'd like to use the flow model of feature branches and separate stable/development branches, but I heavily use the model where branches are merged through GitHub pull requests and the main branch is p…
-
## Reference
- [Git Branch Naming Convention - DEV](https://dev.to/couchcamote/git-branching-name-convention-cch)
- [Git/GitHub branching standards & conventions](https://gist.github.com/digitaljhel…
-
All Developers: Can we agree on the 'git branching model' of nvie?
Links:
http://nvie.com/posts/a-successful-git-branching-model/
https://github.com/nvie/gitflow
http://splitshade.wordpress.com/2012/…
-
## Summary
Use GitFlow in order to develop a new own model of branching.
**Please suggest rules in the comments.**
### Suggestions
- [x] Add protection rules
- [ ] Decide procedure of pul…
-
If the multi module POM (root) and the parent POM are different POMs, the the plugin throws the following error:
> Failed to execute goal com.amashchenko.maven.plugin:gitflow-maven-plugin:1.10.0:r…
-
According to the original Gitflow model a hotfix or release should be merged to both master and develop. But using Git-tower (they send me here since they use gitflow-avh) a hotfix or release branch i…
-
When i use `git flow hotfix finish v1.0`, the new created tag `v1.0` was merged into develop but not `hotfix/v1.0`