Skip to content

Latest commit

 

History

History
55 lines (35 loc) · 3.21 KB

gitflow.md

File metadata and controls

55 lines (35 loc) · 3.21 KB
Raw

Gitflow

Resource Branches

Resource Branches must be created from develop. They can be:

  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • chore: Changes that updates grunt tasks etc. No production code change. Nothing that an external user would see
    • implementation (of an existing feature, which doesn't involve a fix),
    • configuration (like the .gitignore or .gitattributes),
    • private internal methods...
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • docs: Documentation only changes
  • feat: A new feature
  • fix: A bug fix
  • perf: A code change that improves performance
  • refactor: A code change that neither fixes a bug nor adds a feature
  • revert: A code change that reverts any changes made in the past
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • test: Adding missing tests or correcting existing tests

After the task is finished, the developer should upload a pull request to Develop and wait for Code Review for the amount of devs defined at the beginning of the project.

Angular Commit Message Guidelines

Develop

No developer will be able to upload code on this branch directly.

Once the resource branch has been approved, it should be merged into this branch which will serve as an accumulator of new implementations.

Ideally this branch has a CD action, Netlify is recommended for that.

Homolog

Since develop already has all the functionality mapped to a particular release, create a release/1.0.0 branch (Semantic versioning). Created this release branch, go up to an approval environment (which is not develop/staging). You can name it homolog, QA, etc. Remembering that the names of the environments are the least, but the ideal is that these environments are accessible only internally, on the network or behind an authentication where it restricts external access. In each environment it is also ideal to have its own database in order not to "dirty" your production data.

Also keep in mind to ask developers to code so that it is easy to mock e2e requests and automated tests (end-to-end, not unitary or integration, testing using a browser to interact on screen) because here, in addition to the QA review, it would also be good to leave some e2e test automator running.

Production

Attested (approved) by QA and by e2e, merge in main, create the tag with the version given in the approval and be happy with your application fully reviewed and deployed :D

References:

Fluxo de trabalho de Gitflow | Atlassian Git Tutorial

MUST READ A successful Git branching model

Commit Structure

Every commit message is linted by commitlint, make sure to check the Semantic Commit Messages guide.