Feature Request: Auto-cherry-pick changes to file origin branches
- Vorherrschende Sprache
- Go
- Sterne
- 762
- Forks
- 72
- Ø Merge
- 18 Std. 24 Min.
- Gemergte PRs (30 T.)
- 28
Beschreibung
I'm not sure if this aligns with your roadmap, but here's my use case:
When working with stacked branches, I often modify files that were introduced in earlier branches. I want these changes to appear in the branch where the file was first added, not the current branch.
Right now, I manually cherry-pick these commits back to the appropriate branches and restack. This gets tedious.
Requested feature: Automatically detect commits that modify files and group them by "file origin branch" - the branch where each file was first introduced. Then offer to move these commits to their origin branches.
Alternative: Documentation on extending git-spice for custom workflows like this.
Of course I can modify some fork of git-spice in any case.
Is this something others would find useful?
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.