Files marked with checkbox should be staged for commit for consistency with other apps and terminal
See original GitHub issuePlease describe the problem you think should be solved To have a consistent experience with other apps as well as terminal, files marked with checkbox should be staged for commit.
Example:
When I have some files with checkboxes checked, when I run git status
in the terminal I should have those files presented in Changes staged for commit
. Files that are not marked with checkbox should be in the section Changes not staged for commit
.
[Optional] Do you have any potential solutions in mind? You can take an inspiration from SourceTree app which works exactly how I describe it. This is very convenient for me, because I can start marking files to commit and end with the terminal or vice versa.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Stage & Commit Files: git add, git commit, & git log free tutorial
1. In your terminal (Terminal, Git Bash, or Windows Command Prompt), navigate to the folder that is your Git repo. · 2. Enter...
Read more >Git: interactive mode with git-add : git add -p : IDEA-63201
Regarding UI, I like how tig works, it shows both staged and unstaged chunk. You can stage or unstage in each view. Maybe...
Read more >SourceTree for Mac 1.9 – Out Now!
Stage files with checkboxes. You can mark whole files for inclusion in the next commit (stage them in git terms) by checking the...
Read more >MacPorts Guide
Once you have Xcode installed, open a terminal, run xcode-select --install , and click the Install button to install the required command line...
Read more >Jenkins User Handbook
There are also other Jenkins Docker images you can use (accessible through ... Download the latest stable Jenkins WAR file to an appropriate...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you so much for the additional clarification @castus - glad the speed of Desktop is solid for you. And I’m sorry the design choice we made doesn’t work well with your workflow. We have seen people who didn’t previously use Desktop to commit have great luck with it when they tried to do increased parts of their workflow with the app, and you wouldn’t need to contend with the Git index. Anyway, I appreciate the feedback and if it’s something we see significantly more of, we’ll definitely revisit. Thanks again!
I started learning GIT only from the Terminal. There is one very annoying thing for me; when I need to check changes to stage. That’s why I use all GIT clients only for visually check changes and stage/unstage files. All other things (commit, rebase, reset, etc.) I’m doing from the terminal. All GIT clients that I’ve tried (SourceTree, GitKraken, Tower) work with my workflow very well, but they are slow comparing to Github Desktop. I noticed it right away when trying your app. For ex. as iOS developer I need to tackle merge conflicts in project files called
.pbxproj
. That file has more than 100k lines of code. I don’t know how you did it, but GH Desktop is blazing fast showing me the changes in that file 😉 That is why I started to use it. Unfortunately it doesn’t have the ability to synchronise index with the git and it was my big disappointment. This is something so much important to me, that I’m unable to use GH Desktop.