Contribution records
Draft
Contributors

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

Give credit to everyone
tedbow tedbow organization(s): Acquia
aaronmchale AaronMcHale
nod_ nod_ volunteering organization(s): Très Bien Tech
joachim joachim volunteering organization(s): Factorial.io
finnsky finnsky organization(s): Skilld
rkoller rkoller
mabho mabho volunteering organization(s): ImageX
mlncn mlncn organization(s): Agaric customer(s): Drutopia
scott_euser scotteuser volunteering organization(s): Soapbox
geek-merlin geek-merlin organization(s): Geeks4Change, MachbarMacher
joaopauloc.dev joaopauloc.dev organization(s): ImageX
nicxvan nicxvan organization(s): nLightened Development LLC
kentr kentr volunteering
heyyo heyyo
dcam dcam
anybody Anybody volunteering organization(s): DROWL.de
smustgrave smustgrave organization(s): Mobomo
godotislate godotislate volunteering
andre.bonon andre.bonon
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.