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

Set branch upstream

Open
#331 1 comment 12 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Trace the gh stack init and push flow in the Go CLI, starting where a branch is pushed to origin. Confirm the resulting behavior with a stacked branch: the first push should establish its upstream, and subsequent git push, git pull, and git status commands should use or report that association.

Written by the indexing model from the issue text.

Description

bug topic: cli - general

Many tools expect to be able to find the associated upstream for a given branch; gh stack currently manages that internally.

When one does gh stack init some-branch, then at such time as gh stack actually pushes the branch to origin, it should do the equivalent of git push --set-upstream origin some-branch in order to create the association.

This lets the user push future changes with just git push (and check for updates with git pull), as well as letting git status show relative differences.

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.