Contribution records
Contributors

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

Give credit to everyone
clayfreeman clayfreeman organization(s): Library Market
cliddell cliddell
jungle jungle volunteering
longwave longwave organization(s): Full Fat Things
neclimdul neclimdul
alexpott alexpott organization(s): Acro Commerce, Thunder
mrinalini9 mrinalini9 organization(s): Material customer(s): Drupal India Association
catch catch organization(s): Third and Grove
andypost andypost volunteering organization(s): Skilld
jonathanshaw jonathanjfshaw
mxr576 mxr576 organization(s): Pronovix
mikechr mikechr volunteering
dpi dpi organization(s): PreviousNext customer(s): Service NSW
br0ken BR0kEN volunteering organization(s): Drupal Ukraine Community, JAKALA (formerly FFW) customer(s): JAKALA (formerly FFW), Propeople (now part of FFW)
larowlan larowlan organization(s): PreviousNext customer(s): Service NSW
quietone quietone organization(s): PreviousNext
ghost of drupal past GhostOfDrupalPast organization(s): Smartsheet
neslee canil pinto NesleeCanilPinto organization(s): Specbee
krzysztof domański krzysztof_domanski organization(s): abventor
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.