In case you come across, this, run the following in a terminal window:
git config --global http.sslVerify false
Now go back to coding!
Category: Git
Git: Syncing fork repo against upstream repo
In case you need to make sure your forked repo is up-to-date with the original repo (i.e. /git/original/HelloWorld vs /git/anton/HelloWorld), here’s what you need to do in your terminal:
$ git remote -v
$ git remote add upstream git@git.url.io:original/HelloWorld.git
$ git remote -v
$ git fetch upstream
$ git checkout master
$ git merge upstream/master
$ git merge upstream/master
Updating ad3aeb1c..3f5ef884
Fast-forward
pom.xml | 5 +-
26 files changed, 139 insertions(+), 578 deletions(-)Ref: https://help.github.com/articles/syncing-a-fork/
Git cheat sheet
This is a post-in-progress.
To revert local commit:
git reset HEAD~1
To see what is about to be pushed:
git diff --stat --cached origin/master
To add to ignored files:
git update-index --assume-unchanged <files to ignore>
Useful commands:
git status
git log
IntelliJ IDEA: Getting “Fetch failed. Fatal: Could not read from remote repository”
In case you encounter this issue, do the following:
1. Preferences > SSH
2. Make sure SSH executable is set to “Native.” (If already so, switch to “Built-in,” apply it, then switch back to “Native.”)
3. Happy fetching!
Git: Create a duplicate branch of master
I worked on upgrading a web service from JDK 1.6 to JDK 1.8 and was successful (that’s something I need to write a post on); however, I wanted to make sure I could revert back to pre-1.8 in case it breaks in production. The solution was to create a clone or duplicate of master before I merged the branch.
This would then allow me to merge that branch if needed. Here’s how:
git checkout -b java6-branch origin/master
And then, it needs to be pushed so others can access it:
git push origin java6-branch
That’s it. You can double-check by logging into your Git site. 🙂
P.S. Best practice is to name your branches in lowercase and in groupings (i.e. foo/bar1, foo/bar2).