Github desktop add files how to#

I had just added this file 30 mins ago and I double checked my account which hasn't had any upload in 4 days. And no, it's not already uploaded on my origin/main. I click 'commit to main' => error that my files are untracked. I put a title and description for the commit. But I think a more relevant downside is that it prevents features like #1644 from being implemented without reinventing git features inside the app.įirst off I'll admit that I suck at git and probably did something wrong (hence why I'm trying to use the desktop app), but from what I'm seeing, your post is straight up misinformation. So I wanted to let you know my reasoning (above), so that it can at least be reconsidered.īecause, as I said in that issue, it was very surprising and disappointing to me to find out, when I tried Github Desktop the other day, that it stages everything in memory and has nothing to do with the real git index. But I'm convinced it's the wrong design decision, based purely on what I have read here, which he has pointed me to. In the issue I linked to, stated that this design decision is not open for debate, and that's fair, since it's your creation so you get to choose what it is and becomes.

Github desktop add files how to#

When a person knows how to use Github Desktop to commit files/lines, they already understand the git index pretty much fully, at least insofar as it relates to the kind of usage of git that Github Desktop already enables.

In fact, the visualization of staged/non-staged files/lines in Github Desktop is already a complete tutorial of the git index and how it works. I conclude that because the git index is an extremely basic and fundamental part of git. This is actually the real motivation behind these design decisions (see also #1644 (comment)): it's apparently that Github Desktop is a git client mostly for very non-technical users. Seems like this could be done by just syncing the app's state with the git index whenever the app is refocused, or at intervals just to be sure. Let me know if you have any other questions about this. We avoid explicit staging support in the app because we don't want users to have to learn about the index and be conscious of the state of the index when making commits.

finally, make the commit using the summary and description entered.

for each file selected, either stage the whole file, or stage selected lines if the user has chosen to make a partial commit.

reset the index of the Git repository, so that changes by external tools are not accidentally included in your commit.

To ensure Desktop crafts the commit you've chosen, it will go through these steps after you've filled out a commit summary (and optional description): Using the example of the above screenshot, all three files will be committed. To include these files in a commit, you use the checkbox next to each file.

When you have untracked files in a repository, they will appear in the Changes list as files with the green + icon, to indicate these are new files:

GitHub Desktop doesn't support staging of files from in the application, and I'll explain how it's currently working to help illustrate why we've designed the app this way.