Issue
Contribution records
Contributors

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

Give credit to everyone
tenten71
rmcf
mitsuko
fchandler volunteering
gwvoigt organization(s): Northern Commerce
cwyattjibc volunteering
s_leu organization(s): Tag1 Consulting, Inc.
mlzr
dajka
eelkeblok organization(s): iO
briantschu organization(s): Forum One
w01f
drupaldope
robcarr volunteering
kenppx
tinto organization(s): The Savvy Few
rop
heavystonehead
calbasi organization(s): calbasi.net customer(s): Experience Box Spain
weseze volunteering
gaurav.kapoor organization(s): Axelerant customer(s): Drupal India Association
lomale@bluewin.ch volunteering
sébastien-fr volunteering
paul dudink
chris matthews
frank.dev
damien laguerre
danrod organization(s): ESINERGIA
Git commit message
Commit types
  • 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

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.