Contribution records
Draft
Contributors

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

Give credit to everyone
sam152 sam volunteering organization(s): PreviousNext
catch catch organization(s): Third and Grove
bahuma20 bahuma20
rafaelrs rafaelrs organization(s): CI&T customer(s): Johnson & Johnson
deepakrmklm deepakrmklm-git organization(s): TATA Consultancy Services
emanaton emanaton volunteering
mdranove mdranove
dww dww volunteering
pameeela pameeela
vinay_ankireddipalli vinay_ankireddipalli
charginghawk charginghawk organization(s): Pegasystems
pratikshad pratikshadubey
idflood idflood
rob230 Rob230 organization(s): CTI Digital
ejanus erek.janus
Nitish k Nitish_k
dmitry.korhov dmitry.korhov organization(s): EPAM
ion.macaria ion.macaria volunteering
mageshbcet1 mageshbcet1
aaron.ferris aaron.ferris
joel_osc joel_osc
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.