Contribution records
Draft
Contributors

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

Give credit to everyone
catch catch organization(s): Third and Grove
jibran jibran volunteering
penyaskito penyaskito organization(s): Lingotek
nginex nginex organization(s): AnyforSoft customer(s): Dropsolid
_pratik_ k_pratik volunteering organization(s): Specbee customer(s): Drupal India Association
nicodh rkcreation-nicols
rpayanm rpayanm organization(s): Agileana
berdir berdir organization(s): MD Systems GmbH
andypost andypost volunteering organization(s): Skilld
kristiaanvandeneynde kristiaanvandeneynde volunteering organization(s): Factorial.io
nigelcunningham NigelCunningham organization(s): Technocrat
joachim joachim organization(s): Factorial.io
johnpitcairn johnpitcairn
baluertl BaluErtl volunteering organization(s): Cheppers customer(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
wim leers wimleers volunteering organization(s): Acquia
geek-merlin geek-merlin organization(s): Geeks4Change, MachbarMacher
ravi.shankar ravi.shankar organization(s): OpenSense Labs
smustgrave smustgrave organization(s): Mobomo
godotislate godotislate volunteering
phenaproxima phenaproxima 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.