Search code examples
githubgit-flowstrategy-pattern

Using pull request Instead of merge in working on feature branches. Is it git flow?

What i wondered

I want to use pull request than merge in working on feature branches. Is it git flow too?

Why this think is started?

  1. I prefer to use pull request than merge for source code review.

  2. Don't wanna remain 'commit history' of my feature branches in master.

Please show any recommanded git repo. for examples

I want to find repository that following git flow for study about git flow.

Would you recommand any repository on git flow? I will mark star and follow repository yours or others

Solution

  • GitHub's Atom repository is a good example of an open source project where contributors create a branch, commit and push to that branch, and when ready, open a pull request. If the pull request is accepted by the project's owners it is merged. Here is a link to merged pull requests.

    I want to use pull request than merge in working on feature branches. Is it git flow too?

    Creating a new branch, working on that branch, and opening a pull request for review and to eventually merge your changes is best practice for both Git Flow and GitHub Flow.

    I prefer to use pull request than merge for source code review.

    Yes, this is great. You can harness the power of protected branches and required status checks to automate testing and ensure branches cannot be merged until all of your required criteria is met.

    Hope that helped - let me know if this did not answer your questions.