Contribution records
Contributors

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

Give credit to everyone
kevinquillen kevinquillen organization(s): Velir
cashwilliams CashWilliams organization(s): Acquia
karimb KarimB volunteering
xmacinfo xmacinfo organization(s): xMac info
hugronaphor hugronaphor organization(s): Acrosto customer(s): manifesto
kiwimind kiwimind
anavarre anavarre organization(s): Acquia
waliur Waliur
akashkumar07 AkashkumarOSL
sinasalek sinasalek volunteering
voleger voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
Webbeh Webbeh organization(s): Georgia Institute of Technology
jigarius jigarius volunteering
solideogloria solideogloria
jcnventura jcnventura organization(s): 1xINTERNET
b.lammers b.lammers
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.