Issue
Contribution records
Forks management
Issue edit
Draft
Contributors

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

Give credit to everyone
wrg20
robertmartin1961
maplinx volunteering
daveiano volunteering
hikkypo
mistergroove volunteering
glynster
loopy1492
coaston
anybody organization(s): DROWL.de
andysipple organization(s): Kanopi Studios
nkraft organization(s): IQ Solutions
stijnd volunteering
pianomansam organization(s): Rapid Development Group customer(s): Two Men and a Truck
jschref
rcodina
arlina organization(s): Chapter Three (acquired by Kanopi Studios)
btully
pearls
kleve organization(s): Happiness
papagrande organization(s): VTP Ventures customer(s): Fluke Biomedical
raphaelbertrand volunteering
edmoreta customer(s): Lullabot
weseze volunteering
peter pulsifer
nigelcunningham
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.