As a developer, you may come across scenarios when you think that certain SPECIAL files should not be tracked in Git commits. As the first step, commit all changes in your repository and then add those SPECIAL files to .gitignore To remove a file (not delete) from getting tracked in your Git repository use: $ git rm --cached sampleconfig.txt To remove all files that is referenced in your .gitignore use: $ git rm -r --cached . (more…)

Go to your local repository in bash $ git fetch origin $ git reset --hard origin/master To clean and remove untracked files and directories $ git clean -fdx

First checkout Develop branch $ git checkout dev Then, reset it to Master branch $ git reset --hard master Make sure to push the changes by force to make origin/dev to be the same as origin/master $ git push --force origin develop

Point 1) Check if you have followed the below sequence of steps when setting up git in your local workstation $ git init $ git add . $ git commit -am "name of the commit" $ git remote add origin https://github.com/username/repository.git $ git push -u origin master Point 2) Check if .git/config file has the following parameters in it [branch "master"] remote = origin merge = refs/heads/master

Git uses "Transfer-encoding" in POST requests and some proxy servers do not support this encoding by default. When large files are pushed, the git client requires higher http.postBuffer setting. Increase the buffer size to see if the issue is related to it. $ git config --global http.postBuffer 134217728

You get this message when the system is behind a firewall and when the security certificates are blocked. There are two ways to overcome this message and to enable a git pull or git clone. i) Issue the below command from git bash $ git config --global http.sslVerify false OR ii) Add http block in "gitconfig" file to avoid ssl verification [http] sslVerify = false sslCAinfo = /bin/curl-ca-bundle.crt