11/13/2023 0 Comments Github desktop cant commit![]() ![]() On the left-hand side, it will show the files that have been added, removed, or altered. You can see the new changes on the GitHub Desktop application. In this README.md file, there were still references to Nexmo, so I suggested the changes shown in the image below: At the time of writing this tutorial, Vonage is going through a rebrand, changing the Nexmo and OpenTok branding to Vonage branding. Below is an example I have when I created some changes to the README.md file of the Vonage PHP SDK. If you have the repository and branch chosen in your GitHub repository, you should see a screen similar to what’s shown below. You’re now ready to review your changes in GitHub Desktop. clone your repository to your local machine.authorize the application to access your GitHub account and repositories.To download the version for your operating system, click one of the previous links and follow the instructions. GitHub Desktop is available on Windows and macOS. If you don’t know what Git is, please check out the Introduction to Git tutorial. GitHub Desktop is a native application for both Windows and macOS to allow developers to manage their repositories. GitHub is a remote hosting platform that enables developers to store their projects externally. Git is a distributed version control system that allows developers to keep track of all changes to files within their projects. ![]() I think a warning banner (dismissable) if the branch is tracking a remote with a different name might be useful, but it's probably not worth the effort for this niche case.In this tutorial, we will learn how to review code changes in GitHub Desktop, commit these changes and then create a pull request on GitHub. I'm going to go ahead and close this as there's probably not much that can be done in Github Desktop to resolve the confusion. Practically, though, it seems from the command line that the tracking a different remote has little impact since doing git push my-new-branch was creating the remote branch anyway. I'd gotten used to the previous way of doing it as that's a quick and easy way to make branches from a tag (and doesn't have these issues since there's no remote branch to track). So you're right, it appears the way I created the branch leaves it tracking the other branch, and the more correct way would be to do git checkout master git checkout -b my-new-branch. It then gets more confusing because Git Desktop is showing the commits I just pushed as local commits (can undo, no 'View on Github' in history view), even though if I browse to they're there on the named branch as expected. ![]() That's confusing because the second command is what you'd normally use to push a branch created with git -b my-new-branch as well. I tried again and found that both git push origin HEAD and git push origin my-new-branch both create the branch on the remote with commits on the branch I made. The git push always creates the new branch on the remote. Seems like git being a bit strange, as I've used this technique from the command line before without having issues. Thanks for the clarification, that's good detail. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |