Issue
Contribution records
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
demoshane
socialnicheguru
emudojo
le72
energee
ohthehugemanatee
zionduc
mirom
joachim
michaelngodh
couloir007
netw3rker
VenDG
gapple volunteering
bohemier volunteering
ronino volunteering
caminadaf organization(s): CI&T customer(s): Pfizer, Inc.
rafaelpedrosanto organization(s): CI&T
rossb89 organization(s): ComputerMinds
sumitmadan organization(s): QED42
tterranigma
mnico organization(s): TIFON
quondam organization(s): Bounteous
ñull
Mike Koup
john.oltman
nikita.izotov
andre.bonon
imiksu
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.