Make sure you’ve navigated to the right directory (check with ls or dir).Here are quick steps you can try to fix this error: You didn’t initialize the Git repository.Here are some reasons why this error might occur: git, states that you tried to execute a repository-specific command, outside of the Git repository. The error above, fatal: not a git repository (or any of the parent directories). For example, if you run git push -u origin master outside of a git repository, Git will simply not know what to push and where to push.
Most of the Git commands must be executed against a Git repository. The fatal: not a git repository error occurs when you try to run a Git command but are not inside a Git repository.Ī Git repository is a collection of files and information regarding past changes made in them. Kubernetes Cost Optimization Cost Factors, Challenges and Solutions.Kubernetes Rancher Rancher Overview, tutorial and alternatives.
Kubernetes Monitoring Kubernetes monitoring best practices.Exit Codes Understand Kubernetes & Container exit codes in simple terms.Kubectl Cheat Sheet Kubectl commands at your fingertips.Git Errors Solving common Git errors and issues.5xx Server Errors Troubleshooting and fixing 5xx server errors.Kubernetes Lens Kubernetes management tools: Lens vs.Kubernetes Architecture Exploring the building blocks of Kubernetes.Kubernetes Troubleshooting Expert tips for debugging Kubernetes.Kubernetes Kubernetes 101: A comprehensive guide.Commit the change to the reverted file.Type git checkout - path/to/file and hit enter.In the terminal, change directories to the working directory.Find the path to the file you want to revert from the working directory.Find the commit ID of the version of the file you want to revert to.
To revert a single file to a specific version do the following: Then you can push that commit to the remote so that the version of your branch on GitHub matches your local version. This done with the standard commit command: In this case, the change is a revert of a single file. But once we revert the file, we need to commit that change. We didn't want a new commit for the file we reverted. I know what you're thinking, "Wait a minute, I thought the whole point was to not create a new commit?" Well that's half true. If I were going to revert the file in the screenshots above, that would look like this: The format of the git command will look like this: Once you've opened a terminal and changed to the working directory, you use git checkout to revert the file. Because of this, you only want the underlined portion.Īll that is left is to revert the file. The first directory listed is the working directory name, and will be the directory you're in when using this file path. Notice I only underlined part of the path. This part is easy because the path to the file is on the same GitHub screen where you found the commit ID for the file.Ībove you can see the same screenshot from before, but this time I've underlined the file path. The next thing you need is the path to the file from the working directory. Either write this commit ID down, or copy it to your clipboard. That is the commit ID for the most recent commit in which that file was modified. On the right hand side you can see a 7 digit commit ID and a date. Once you navigate to the file, right above the file you should see this: Reverting the file is a much cleaner what to handling it.įirst you need to go to the shared repository on GitHub and find the file that you want to revert.
#Revert this commit github desktop code#
However, manually changing each line of code in those files back to their original state and doing a new commit can lead to a messy commit history. This need arises because you sometimes need to change files not related to you're pull request in order to test the feature you're working on.
#Revert this commit github desktop how to#
Once you start collaborating with other developer it's going to be important to know how to revert a single file to a certain commit.
0 kommentar(er)
