Issue
Contribution records
Contributors

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

Give credit to everyone
cilefen
heni_deepak
lpeidro organization(s): Metadrop
imclean
gordon organization(s): Heydon Consulting customer(s): Department of Customer Service, NSW
smustgrave organization(s): Mobomo
loon volunteering organization(s): DevBranch, Drupal Ukraine Community customer(s): Evolving Web
azinck organization(s): Forum One
alexpott organization(s): Acro Commerce, Thunder
catch organization(s): Third and Grove
nod_ organization(s): Très Bien Tech customer(s): OPTASY, Palantir.net
longwave organization(s): Full Fat Things
kelly.m.jacobs volunteering organization(s): Kalamuna
abhijith s volunteering organization(s): Zyxware Technologies
qusai taha organization(s): Vardot
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.