Issue
Contribution records
Contributors

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

Give credit to everyone
roderik volunteering organization(s): Cheppers customer(s): Acquia
dawehner
larowlan volunteering organization(s): PreviousNext
catch organization(s): Third and Grove
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
klemendev volunteering
quietone volunteering organization(s): Acro Commerce
ofry volunteering
mohit_aghera volunteering organization(s): Axelerant
rewted
Ruedische
abramm organization(s): DevBranch, Drupal Ukraine Community
ao2 volunteering
hchonov organization(s): bio.logis Genetic Information Management GmbH
mayurjadhav organization(s): Material
nplowman
paranojik organization(s): Amazee Labs
rollins organization(s): DevBranch, Drupal Ukraine Community
scalas89
benjifisher volunteering
samiullah organization(s): Salsa Digital
himynameisseb organization(s): Investis Digital
dionsj volunteering
lupusgr3y organization(s): Novicell
jonathanshaw
xjm organization(s): Acquia
longwave organization(s): Full Fat Things
dylan donkersgoed organization(s): Northern Commerce
deepak goyal organization(s): Material customer(s): Drupal India Association
dmytro-aragorn
vadim.hirbu organization(s): JAKALA (formerly FFW)
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.