Contribution records
Contributors

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

Give credit to everyone
JacobSingh JacobSingh
Myriam974 Myriam974
jerrac jerrac
interaxsys interaxsys
bryancasler animelion
rinodods rinodods
pazap47 pazap47
electroponix electroponix
luisdesig luisdesig
califsurferboy33 califsurferboy33
todos27 todos27
kscott22 kscott22
jonabh yuval.j.benhur
leducdubleuet LeDucDuBleuet volunteering
twod twod volunteering
ricovandevin ricovandevin organization(s): Finlet
niek_kloots Niek_Kloots volunteering
DavidoffC DavidoffC
shinz83 shinz83
Dev_sayed Dev_sayed
james.elliott jameselliott
Jayson Wonder Jayson_Wonder
Amad Tababa lecooper-ly
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.