We should not just put "Save uncommitted changes" when I say "Commit changes"...

Open
#3,534 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
git, github
Domain
desktop, frontend

Research direction

Reproduce the behavior in the GitHub app at /chat using a local branch and the “Commit changes” action. Compare the current “Save uncommitted changes” wording with the requested commit flow, and consider the work complete when the UI lets the user request a better commit message instead of only saving uncommitted changes.

Written by the indexing model from the issue text.

Description

We should not just put "Save uncommitted changes" when I say "Commit changes" in the UI in local branch, it should allow me to allow github to make a better commit message


Field Value
App version 1.1.14
OS macOS 26.6.2
Theme GitHub
Path /chat
Tenure Week 9
Dominant language
No language data
Stars
2.1k
Forks
157
PR merge metrics
No merged PRs in 30d

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/app

All issues in github/app

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.