Issue
Contribution records
Contributors

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

Give credit to everyone
Drupaldev2013
joekers organization(s): Zoocha
cilefen
rajanvalecha12 volunteering
aleevas organization(s): Skilld
audacus organization(s): Previon Plus AG
ddhuri volunteering
mulukallaarun
cobenash
dpi
phenaproxima organization(s): Acquia
robbmlewis volunteering
kndr volunteering
dgaspara organization(s): NTT DATA
timfletcher volunteering
iamweird organization(s): Attico International
marcoscano volunteering organization(s): Lullabot
danflanagan8 organization(s): Nerdery
larowlan organization(s): PreviousNext customer(s): Service NSW
loopy1492
nicolas s.
michèle
kristen pol organization(s): Itty Bitty Byte
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.