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

Allow editing commit messages when merging a stack

Open
#493 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start at the website flow that merges a stack of PRs and compare it with the existing single-PR merge prompt. The work is done when stack merges allow an editable commit message, including squash merges, while preserving the current behavior for individual PRs and avoiding the verbose default message described in the issue.

Written by the indexing model from the issue text.

Description

Generally loving all the new stack features, thank you! To make it more useful, it would be great if when merging a stack of PRs from the website if we were prompted to choose a commit message like we are if merging one PR at a time.

For further details, we require squash merges and I have a coworker who performs a ton of tiny commits per branch in the stack. The default commit message for the squash merges includes a separate line per commit + blank lines around each; this ends up as a LOT of vertical space in the standard git log output that is really unhelpful.

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.