2

For example, if I am working on a git/github repo alone and have two branch (master and develop) and I make some commits to develop branch.

So should I go for git merge or pull requests and what are their benefits

Yashu Mittal
  • 1,034
  • 1
  • 7
  • 30
  • This is a common question, see some other discussion here: https://stackoverflow.com/questions/22199432/pull-request-vs-merge-request – Shane Burroughs Feb 16 '18 at 18:33
  • I have read that question, but I was still in doubt that pull request should be used if you are working in a team. – Yashu Mittal Feb 16 '18 at 19:15

1 Answers1

1

By creating pull requests, you have a proper logging of your merges, which you can monitor via the Pull Requests section in GitHub. In the end, you end up merging your develop branch to the master.

Another approach can be, keep your master clean, and always work on the develop branch, and to push your changes to master, just rebase, and bring your both branches to level.