The correct answer is actually so simple. You don’t need to checkout anything, neither do you have to resort to COMMIT_HASH hacks (which don’t work on Cedar stack). All you need to do is: git ls-remote <remote> > git ls-remote heroku ddaszxcewb585d3a3c00de816a197b14462791a3 HEAD ddaszxcewb585d3a3c00de816a197b14462791a3 refs/heads/master
You’ve got the syntax for the scp-style way of specifying a repository slightly wrong – it has to be: [user@]host.xz:path/to/repo.git/ … as you can see in the git clone documentation. You should use instead the URL: git@skarp.beanstalkapp.com:/gittest.git i.e. in the URL you’re using, you missed out the : (colon) To update the URL for origin … Read more
When you use git push origin :staleStuff, it automatically removes origin/staleStuff, so when you ran git remote prune origin, you have pruned some branch that was removed by someone else. It’s more likely that your co-workers now need to run git prune to get rid of branches you have removed. So what exactly git remote … Read more
You may need to prune your local “cache” of remote branches first. Try running: git fetch -p origin before deleting.
If the git repo is in github, open any file in the repo, then click ‘edit’, github will show something like this: You’re editing a file in a project you don’t have write access to. We’ve created a fork of this project for you to commit your proposed changes to. Submitting a change to this … Read more
There was almost the same question on GitHub a year ago. The idea was to rename the master branch: git branch -m master development git branch -m published master git push -f origin master Making master have what you want people to use, and do all other work in branches. (a “git-symbolic-ref HEAD refs/head/published” would … Read more
I recommend using git branch –format to specify the exact output you want from the git branch command. By doing that, you can pull out just the refname and the upstream, like this: git branch –format “%(refname:short) %(upstream)” It outputs the branches along with the remote branches if they exist, in the following format: 25-timeout-error-with-many-targets … Read more
I’ve found this one: git push rorg ‘refs/remotes/korg/*:refs/heads/*’ And it pushed all my remote branches from korg to rorg (even without local copies of the branches). See the output below: Counting objects: 293, done. Delta compression using up to 4 threads. Compressing objects: 100% (67/67), done. Writing objects: 100% (176/176), 48.32 KiB, done. Total 176 … Read more
git pull is probably creating the commit. If you make a local commit and then run git pull after someone else pushes a commit up to the repository, Git downloads the other developer’s commit and then merges it into your local branch. How to avoid these merge commits in the future You could use git … Read more
This is the command that you need to execute on the mirror: git remote update