Source: lnahum.medium.com
Git Takes Sha Instead Of Remote Branch
as debugging a weird production issue. the version deploy was absolutely wrong.
in our CI it was a running integer but in the repo I created for the example it will be 2c4f227 by coincidence it was starting the same way as a random commit on the main branch.
All new commits will be added to the tip of this branch.’when: git checkout‘Updates files in the working tree to match the version in the index or the specified tree. If no pathspec was given, git checkout will also update HEAD to set the specified branch as the current branch.’ see this stack overflow Q&A for a better explanation: https://stackoverflow.com/questions/57123031/git-checkout-commit-hash-vs-git-checkout-branch/
in our CI it was a running integer but in the repo I created for the example it will be 2c4f227 by coincidence it was starting the same way as a random commit on the main branch.
All new commits will be added to the tip of this branch.’when: git checkout‘Updates files in the working tree to match the version in the index or the specified tree. If no pathspec was given, git checkout will also update HEAD to set the specified branch as the current branch.’ see this stack overflow Q&A for a better explanation: https://stackoverflow.com/questions/57123031/git-checkout-commit-hash-vs-git-checkout-branch/
Related Articles
Community Partners
DevOps Careers