"Development" branch doesn't update after release with `toReleaseBranch` merge strategy
See original GitHub issueI’ve found new bugs with toReleaseBranch
merge strategy, while I had tested #777 issue.
Describe the bug
Development
branch doesn’t update after release with toReleaseBranch
merge strategy
To Reproduce Steps to reproduce the behavior:
- setup merge strategy
toReleaseBranch
- release new version
- get outdated version of development branch
Expected behavior
development branch should be updated in the end of release, but now ship.js
push updates to release
branch instead of development
Links
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Git branching strategy - losing changes on merge
The best practice is to rebase a dev branch on top of their intended merge target ( QA or release ), and then...
Read more >Gitflow release branch process from start to finish example
It is only created when the develop branch is feature complete, and it is merged with the master branch once final testing is...
Read more >Git branches: Merging issues while having multiple release ...
As soon as you decide that the release X is not going to be getting updates from master you can't merge your fixes...
Read more >Using a Branching Strategy That Works - Cocoacasts
A feature branch starts its life on develop and, once the feature is ready to be released, the changes are merged into develop...
Read more >Don't Fear the Repo: Enhanced Git Flow Explained - Toptal
Release and hotfix branches require “double merging”—once into main, then into develop. At times you can forget to do both. You can make...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you all. I got confused. I’m releasing the fix now! 😃
Released in 0.18.4 🙂