Issue
Contribution records
Contributors

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

Give credit to everyone
giancarlosotelo organization(s): MD Systems GmbH
webchick organization(s): Acquia
Benia
berdir organization(s): MD Systems GmbH
jhedstrom organization(s): Phase2 customer(s): Memorial Sloan Kettering Cancer Center
andypost volunteering organization(s): Skilld
sime
mstrelan
juampynr organization(s): Lullabot
rphair volunteering
toelli
ksavoie
agoradesign
bloomt
mrf organization(s): Chapter Three (acquired by Kanopi Studios)
geerlingguy
ressa organization(s): Ardea
damienmckenna organization(s): Current
jesse.voogt organization(s): Plethora
dave reid
bart vanhoutte organization(s): Duo
elijah lynn
wim leers organization(s): Acquia
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.