![]() Type in a descriptive message and press Enter. Once clicked, you’ll be asked to enter a commit message into the Command Palette near the top of the VS Code window. When you’re ready to commit the changes, click the checkmark icon near the heading Source Control: Git.At any rate, in this screen shot, I clicked the Stage Changes icon (the plus (+) sign), and now we can see that an index of changes have been added.At least, that’s the way I understand it… If a commit were to be performed while the second feature is still being developed, only the staged changes would be committed to the online repository. And you can continue working on the second feature after you’ve staged the progress made on the first feature. Once you get the first feature working, you can stage the changes to help track progress. The one feature is now working, but the second feature still needs some additional work. ![]() I was confused about staging files in the beginning, but the way I understand it is this: Let’s say you’re working on a script that has two features.At this point, you can discard those changes, stage the changes, or commit the changes directly to the online repository (skipping the whole staging process completely).I believe the U at the tail end of the file name means that the file is new and not tracked by GitHub yet. If we click on that Source Control icon, we can see that there’s now a change pending for that file. Now in VS Code, the file name appears in green text, and a new bubble icon has appeared over the Source Control icon. ![]() In this example, I’ll create a new file called sample-file.txt.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |