Issue
Contribution records
Contributors

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

Give credit to everyone
pounard
fabianx organization(s): Tag1 Consulting, Inc. customer(s): The Linux Foundation
marcingy
amateescu customer(s): Drupal Association
joelpittet
discipolo
mikeytown2
damienmckenna organization(s): Current
ndobromirov
dreamer777
hosef organization(s): Hook 42
oadaeh organization(s): Hook 42
David_Rothstein volunteering
mustanggb
mxr576 organization(s): Pronovix
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): The Linux Foundation
quietone organization(s): Acro Commerce
joshmiller organization(s): Acro Commerce
izmeez
ronino volunteering
potop
mcdruid volunteering organization(s): Acquia
gbirch
phizes organization(s): Wunderman Thompson Technology
btully
mforbes
Jordan Samouh
boyan.borisov organization(s): JAKALA (formerly FFW) customer(s): LUSH Digital
das-peter organization(s): Cando
joseph.olstad
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.