Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`gh stack sync` always rebases, which breaks PR review history

Open
#354 7 comments 29 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
git, github, go
Domain
cli, developer-experience

Research direction

Start at the implementation and tests for gh stack sync; reproduce a sync where upstream changes exist and compare the current rebase behavior with a merge. Done means the command supports the requested non-rewriting behavior, with its option or default settled and tests covering the resulting history.

Written by the indexing model from the issue text.

Description

feature request topic: rebase alternative

If a reviewer has already viewed/reviewed a PR, and the submitter performs a gh stack sync, it will then force-push, which erases useful information about "changes since last view" in the PR interface.

It should be an option (the default?) to perform a merge from upstream rather than a rebase to avoid messing up the review history.

Dominant language
Go
Stars
1.5k
Forks
73
Avg merge
1d 8h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-stack

All issues in github/gh-stack

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.