Issue
Contribution records
Contributors

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

Give credit to everyone
markhalliwell organization(s): Tag1 Consulting, Inc.
isilweo
RobKoberg
shaundychko
wooody
rerooting
benjarlett
kclarkson
bdanin
hkirsman
hmartens
jurriaanroelofs
Sherbet
c13l0
wrender volunteering
birdsnbees
lukasss
wundo organization(s): Chuva Inc.
eidoscom volunteering
xaa volunteering organization(s): Deepmedia, WebstanZ
albertski volunteering
macmladen volunteering
travisc
slipperysky
makazimtingwa volunteering
kentr volunteering
pakmanlh organization(s): Ymbra
rodrigoaguilera organization(s): Ymbra
sylus
chandeepkhosa organization(s): 2Toucans
lunk rat
Chris Charlton volunteering
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.