Issue
Contribution records
Contributors

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

Give credit to everyone
webchick
kbahey
Akaoni
catch
dries
yoroy
chx
sun
rbayliss
synth3tk
oriol_e9g
gdd
David_Rothstein
NROTC_Webmaster
randomtide
heddn
jhedstrom
20th
rjzaar
dww organization(s): TEN7
quietone organization(s): PreviousNext
kostyashupenko organization(s): Skilld
acbramley organization(s): PreviousNext customer(s): Service NSW
smustgrave organization(s): Mobomo
poker10 organization(s): ActivIT s.r.o.
dave reid
Paul Simard
kim.pepper organization(s): PreviousNext
larowlan organization(s): PreviousNext
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.