Github does not provide such functionality. Github repositories are either public or private, both not both. However, if the part you want to share is small enough (let’ say 4-5 files) you can create a public gist. Unfortunately, there is no way to update the gist automatically.
git push assumes that you already have a remote repository defined for that branch. In this case, the default remote origin is used. git push origin master indicates that you are pushing to a specific remote, in this case, origin. This would only matter if you created multiple remote repositories in your code base. If … Read more
From the git-config man page: remote.<name>.url The URL of a remote repository. See git-fetch(1) or git-push(1). remote.<name>.pushurl The push URL of a remote repository. See git-push(1). Try setting the former to an http: url and the latter to a git+ssh: (or just git:) url?
There is currently no way to use git push to create a repository on the remote. The best you can do is write a one-liner script something like this: #!/bin/bash ssh $1 “git init –bare $2” && git push ssh://$1/$2 Hopefully you can ssh in; if you can’t, you could use some kind of filesystem … Read more
Use an HTTPS or SSH URL. Instead of git://github.com/user/repo.git use one of these: https://github.com/user/repo.git [email protected]:user/repo.git You can change it in your clone like this: git remote set-url origin <THE-URL-HERE>
The closest option may be: git push –follow-tags Push all the refs that would be pushed without this option, and also push annotated tags in refs/tags that are missing from the remote but are pointing at committish that are reachable from the refs being pushed.
The term “right answer” is a bit ambiguous in this case. I actually think that “all revs reachable from newrev but nowhere else” is completely correct. This is true even if there was a merge – in that case, you should see the commits unique to the new ref, and the merge commit, but not … Read more
This is easy to do with Git with a pre-receive hook. Of course, this requires that you are actually able to install hooks, and for obvious reasons, GitHub doesn’t allow you to upload arbitrary executable files to run on their servers 🙂 In general, the workflow with Git or really any distributed version control system, … Read more
Add a new remote (say, other) in your own repo. Pull other/<branch> changes into your local branch (say, add-other-changes). Push to your own forked repo (origin/add-other-changes). Now, when’re you done with add-other-changes branch, create a Pull request & merge it with origin/master. Pull other repo’s changes into your own repo: # go into your own … Read more