-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
submit: Include merged CRs in navigation comments (#508)
This change adds merged CRs to navigation comments. When a CR is merged, its upstacks will still report it in their nav comment even when they're rebased and resubmitted. To do that git-spice now keeps track of merged PRs in the per-branch state of the bottom branch in each stack. This then gets bubbled up to all branches directly above it when that branch is merged. The state is currently propagated from `repo sync`. Two special-cases are added: - `stack edit` and `downstack edit` will transfer the merged history to the new bottom-most branch - `branch create --below` from the bottom-most branch will transfer merge history to the new bottom-most branch In the future, we may need to introduce a shared space for tracking branch and CR history instead of in dependents. (e.g. a place where all branches, current and former are tracked, maybe with some garbage collection.) Resolves #331 --------- Co-authored-by: Abhinav Gupta <[email protected]>
- Loading branch information
1 parent
28d0458
commit 618a3f8
Showing
17 changed files
with
1,028 additions
and
63 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
kind: Added | ||
body: >- | ||
submit: Include merged changes in navigation comments | ||
when restacking and resubmitting changes based on them. | ||
time: 2024-12-01T20:54:46.755566Z |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.