Feature request
gh stack rebase currently invokes git rebase without passing through date-related flags. It would be useful to support --reset-author-date and/or --committer-date-is-author-date so users can control how commit timestamps are handled during cascade rebases.
Current behavior
git rebase and git rebase --onto are called with no date flags:
internal/git/gitops.go — Rebase(): runSilent("rebase", base)internal/git/gitops.go — RebaseOnto(): runSilent("rebase", "--onto", newBase, oldBase, branch)
Commit timestamps follow git's default rebase behavior. There is no way to pass date-related flags through gh stack rebase.
Proposed behavior
Add optional flags to gh stack rebase:
--reset-author-date — forwards --reset-author-date to the underlying git rebase calls--committer-date-is-author-date — forwards --committer-date-is-author-date to the underlying git rebase calls
These should be forwarded to both Rebase() and RebaseOnto() calls throughout the cascade rebase, including --continue flows.
Use case
When rebasing stacked branches, the committer date can become significantly newer than the author date, causing commits to appear out of chronological order in tools that sort by committer date. Having control over date handling during gh stack rebase would keep commit history clean and consistent.
Feature request
gh stack rebasecurrently invokesgit rebasewithout passing through date-related flags. It would be useful to support--reset-author-dateand/or--committer-date-is-author-dateso users can control how commit timestamps are handled during cascade rebases.Current behavior
git rebaseandgit rebase --ontoare called with no date flags:internal/git/gitops.go—Rebase():runSilent("rebase", base)internal/git/gitops.go—RebaseOnto():runSilent("rebase", "--onto", newBase, oldBase, branch)Commit timestamps follow git's default rebase behavior. There is no way to pass date-related flags through
gh stack rebase.Proposed behavior
Add optional flags to
gh stack rebase:--reset-author-date— forwards--reset-author-dateto the underlyinggit rebasecalls--committer-date-is-author-date— forwards--committer-date-is-author-dateto the underlyinggit rebasecallsThese should be forwarded to both
Rebase()andRebaseOnto()calls throughout the cascade rebase, including--continueflows.Use case
When rebasing stacked branches, the committer date can become significantly newer than the author date, causing commits to appear out of chronological order in tools that sort by committer date. Having control over date handling during
gh stack rebasewould keep commit history clean and consistent.