Contribution records
Contributors

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

Give credit to everyone
joelpittet joelpittet
lewisnyman lewisnyman organization(s): Mearra (formerly known as Wunder)
berdir berdir
lauriii lauriii
idebr idebr
bruvers Danis organization(s): Mearra (formerly known as Wunder)
kylebrowning kylebrowning
snap_x Snap organization(s): DevBranch
andypost andypost volunteering organization(s): Skilld
nod_ nod_ volunteering
xjm xjm volunteering organization(s): Acquia, xjm
droplet droplet
komalk kkolekar organization(s): Material customer(s): Drupal India Association
jproctor jproctor
acbramley acbramley organization(s): PreviousNext
wim leers wimleers organization(s): Acquia
manjit.singh Manjit.Singh
henrijs.seso mansspams organization(s): Mearra (formerly known as Wunder)
alexpott alexpott organization(s): Acro Commerce, Thunder
catch catch organization(s): Tag1 Consulting, Inc.
cilefen cilefen volunteering
effulgentsia effulgentsia organization(s): Acquia
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.