Git – Pull request without forking

branchgitgithubrepository

Here are steps of code contribution from the topic "How do I contribute to other's code in GitHub?"

Fork the project
Make one or more well commented and clean commits to the repository. You can make a new branch here if you are modifying more than one part or feature.
Perform a pull request in github's web interface.

Is it possible to make a pull request without forking a repo?

It's quite sad to see more than 20 repos in my account which were forked for some pull requests. They have no activity then and zero stars / followers. Looks like I'm just copying somebody's code for a black day.

Best Answer

If you don't have access to create branches on that repository, there is no way to create a pull request without forking.

Related Solutions

Git – the difference between ‘git pull’ and ‘git fetch’

In the simplest terms, git pull does a git fetch followed by a git merge.

You can do a git fetch at any time to update your remote-tracking branches under refs/remotes/<remote>/. This operation never changes any of your own local branches under refs/heads, and is safe to do without changing your working copy. I have even heard of people running git fetch periodically in a cron job in the background (although I wouldn't recommend doing this).

A git pull is what you would do to bring a local branch up-to-date with its remote version, while also updating your other remote-tracking branches.

From the Git documentation for git pull:

In its default mode, git pull is shorthand for git fetch followed by git merge FETCH_HEAD.

Git – Default behavior of “git push” without a branch specified

You can control the default behavior by setting push.default in your git config. From the git-config(1) documentation:

push.default

Defines the action git push should take if no refspec is given on the command line, no refspec is configured in the remote, and no refspec is implied by any of the options given on the command line. Possible values are:

nothing: do not push anything
matching: (default before Git 2.0) push all matching branches

All branches having the same name in both ends are considered to be matching.
upstream: push the current branch to its upstream branch (tracking is a deprecated synonym for upstream)
current: push the current branch to a branch of the same name
simple: (new in Git 1.7.11, default since Git 2.0) like upstream, but refuses to push if the upstream branch's name is different from the local one

This is the safest option and is well-suited for beginners.

The simple, current and upstream modes are for those who want to push out a single branch after finishing work, even when the other branches are not yet ready to be pushed out

Command line examples:

To view the current configuration:

git config --global push.default

To set a new configuration:

git config --global push.default current

Best Answer

Related Solutions

Git – the difference between ‘git pull’ and ‘git fetch’

Git – Default behavior of “git push” without a branch specified

Related Topic