Contribution records
Contributors

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

Give credit to everyone
amitaibu amitaibu
summit summit
BenK benk
reecemarsland reecemarsland
guybedford guybedford
noslokire noslokire
kclarkson kclarkson
bradjones1 bradjones1
infines infines
capellic capellic
facal facal
mzwyssig mzwyssig
cesareaugusto cesareaugusto
damienmckenna damienmckenna organization(s): Current
dimitriseng dimitriseng
jmones jmones
jenlampton jenlampton
Stilicone Stilicone
Tsubo david-carry
meba meba
jherencia jherencia
rbrownell ryanbrownell
drewallen drewallen
finex finex
forgottenbas forgottenbas
andrewko andrewko
anu03 anu03
clashar clashar
bruceci bruceci
dasha_v dashav
dave reid davereid
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.