Issue
Contribution records
Contributors

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

Give credit to everyone
larowlan volunteering organization(s): PreviousNext customer(s): Charles Darwin University
jibran volunteering organization(s): Department of Customer Service, NSW, PreviousNext customer(s): Service NSW
hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
aaronmchale
dpi volunteering organization(s): PreviousNext customer(s): Service NSW
johnwebdev
psf_ organization(s): SDOS
jonathanshaw
berdir organization(s): MD Systems GmbH
xjm organization(s): Acquia
nevergone
smustgrave organization(s): Mobomo
nwom
kristiaanvandeneynde organization(s): Factorial.io customer(s): Global Game Jam
acbramley organization(s): PreviousNext customer(s): Service NSW
anybody organization(s): DROWL.de
bbrala organization(s): SWIS
catch organization(s): Third and Grove
bnjmnm organization(s): Acquia
mstrelan
lukus
darvanen
alison
wim leers organization(s): Acquia
ravi.shankar organization(s): OpenSense Labs
manuel garcia volunteering
akhildev.cs volunteering organization(s): Zyxware Technologies
kim.pepper 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.