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

Make submit shortcut configurable (or change default from `Ctrl+S`)

Open
#383 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the stack submission UI and the handler for the current Ctrl+S shortcut, then inspect how gh-stack receives terminal input. Decide on the supported binding behavior from the proposal and verify that submission works with the chosen shortcut without relying on Ctrl+S.

Written by the indexing model from the issue text.

Description

feature request topic: cli - submit
Summary

In the stack submission UI, Ctrl+S is used to submit to GitHub. Could we make this shortcut configurable (and/or consider a different default)?

Problem

Ctrl+S commonly maps to "save" in many terminal editors/tools, and in some terminal environments it can conflict with user expectations or existing keybindings. This can lead to accidental submissions or friction when switching contexts. In my case I was unable to submit my stack since Ctrl+S is being hijacked by my terminal and the gh TUI was never able to receive it.

Proposal

One of the following (in order of preference):

  1. Add configurable keybindings for TUI actions (including submit), with a sensible default.
  2. Keep Ctrl+S as an optional binding but add an additional default (e.g. Enter on focused submit, Ctrl+Enter, or s in a specific mode).
  3. If full keybinding customization is out of scope, switch the default submit shortcut to a less collision-prone key combo.
Additional context

Current behavior observed in stack submission flow where Ctrl+S triggers submit.

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.