René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support gh stack rebase --reset-author-date / --committer-date-is-author-date passthrough","articleBody":"## Feature request\n\n`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.\n\n## Current behavior\n\n`git rebase` and `git rebase --onto` are called with no date flags:\n\n- `internal/git/gitops.go` — `Rebase()`: `runSilent(\"rebase\", base)`\n- `internal/git/gitops.go` — `RebaseOnto()`: `runSilent(\"rebase\", \"--onto\", newBase, oldBase, branch)`\n\nCommit timestamps follow git's default rebase behavior. There is no way to pass date-related flags through `gh stack rebase`.\n\n## Proposed behavior\n\nAdd optional flags to `gh stack rebase`:\n\n- `--reset-author-date` — forwards `--reset-author-date` to the underlying `git rebase` calls\n- `--committer-date-is-author-date` — forwards `--committer-date-is-author-date` to the underlying `git rebase` calls\n\nThese should be forwarded to both `Rebase()` and `RebaseOnto()` calls throughout the cascade rebase, including `--continue` flows.\n\n## Use case\n\nWhen 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.","author":{"url":"https://github.com/Kick-snare","@type":"Person","name":"Kick-snare"},"datePublished":"2026-04-16T07:04:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/34/gh-stack/issues/34"}