Contribution records
Contributors

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

Give credit to everyone
mmjvb mmjvb volunteering
anybody Anybody organization(s): DROWL.de
ressa ressa organization(s): Ardea
heddn lucashedding organization(s): MTech, LLC
megakeegman MegaKeegMan organization(s): Agaric customer(s): Drutopia, Portside
_kash_ _KASH_
larowlan larowlan organization(s): PreviousNext
amitvin amitvin
niko niko
wheelercreek wheelercreek volunteering
jepster_ jepSter organization(s): publicplan GmbH
kristen pol kepol organization(s): QuantCDN, Salsa Digital
niko- niko- volunteering organization(s): Skilld
amber himes matz amberhimesmatz volunteering
sudesh.solaskar sudesh.solaskar volunteering
fathima.asmat fathima.asmat volunteering
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.