Issue
Contribution records
Contributors

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

Give credit to everyone
junedkazi
marcingy
dawansv
merlinofchaos
nachenko
colan organization(s): Colan Schwartz Consulting customer(s): Chapter Three (acquired by Kanopi Studios)
rv0
neuquen
dhalbert volunteering
adwuk
donaldp volunteering
hawkdavis
BigBrother2010
dman volunteering
cilefen
niek_kloots
func0der
pvasili
kaztur
francoud
lotyrin volunteering
webservant316
oriol_e9g organization(s): Diputació de Barcelona
keesje
dawehner volunteering
catch volunteering
svdhout
arx-e
Jedd Casella
Rafal Lukawiecki
Git commit message
Commit types
  • 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

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.