The document discusses combining the GitFlow workflow with pull requests. It recommends adapting the workflow to your project rather than conforming your project to a workflow. It emphasizes that pull requests are important for clearly describing features, grouping commits by functionality, and closing related issues, while code reviews help test features, refactor code, assist new developers, produce cleaner code, and support learning.

1. GitFlow + Pull Requests
Fundamentals
A useful Git workflow to start with
Carlos Cavero
Special acknowledge to Mario Rodríguez
This work is licensed under the Creative Commons Attribution Non Commercial Share Alike 3.0 License. To view a copy of this license, visit
https://creativecommons.org/licenses/by-nc-sa/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco,
California, 94105, USA.

2. Git Workflow
Fundamentals
Different git workflows for different needs

3. GitFlow
Workflow
(Atlassian)
Copyright of atlassian gitflow

4. GitHub
Workflow
https://guides.github.com/introduction/flow/index.html

5. GitLab
Workflow
https://docs.gitlab.com/ce/workflow/gitlab_flow.html

6. GitFlow + Pull Requests
Adapt the wokflow to your project and no the
other way round

7. GitFlow Workflow
(Atlassian) +Pull
Requests
Copyright of atlassian gitflow
PULL REQUEST

8. How important
arePullRequests
andCode
Reviews
PULL REQUEST
 Clearly describe how the feature was implemented
 Use template to guide you in the process
 Group the commits by functionality to keep consistence
 Close the issue
CODE REVIEW
 Test the feature and check that the code needs refactoring
 Use tools such SonarQube, Lint and so on
 Experienced developers help newbies
 The code is cleaner because you expect to be reviewed
 Learn, learn, learn

9. Thanks!
For more information please contact:
carlos.cavero@atos.net