We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have nested feature branches:
main \ feature1 \ feature2
Git Town knows the branch hierarchy.
I submit a PR for feature1, the maintainer merges my MR and deletes the branch on the remote.
feature1
On the next sync, Git Town should update feature2 to have the parent main.
feature2
main
The text was updated successfully, but these errors were encountered:
I came here to say that this is exactly my workflow and a much wanted feature.
Sorry, something went wrong.
This would also allow the PR author to merge its own PR on the GitHub interface, without having to use ship.
ship
This should work in the upcoming v10 release: https://github.com/git-town/git-town/blob/main/features/sync/current_branch/feature_branch/tracking_branch_deleted/features/multiple_ancestors_shipped.feature
No branches or pull requests
I have nested feature branches:
Git Town knows the branch hierarchy.
I submit a PR for
feature1
, the maintainer merges my MR and deletes the branch on the remote.On the next sync, Git Town should update
feature2
to have the parentmain
.The text was updated successfully, but these errors were encountered: