Issue
Contribution records
Contributors

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

Give credit to everyone
mark_fullmer volunteering organization(s): University of Texas at Austin
sarwan_verma organization(s): Virasat Solutions
ankitv18 volunteering organization(s): Acquia
berdir organization(s): MD Systems GmbH
mingsong volunteering
safetypin
cb_govcms
kreynen organization(s): University of Denver
hesnvabr organization(s): Material customer(s): Drupal India Association
smustgrave organization(s): Mobomo
guilmour-asc organization(s): CI&T
shiraz dindar
jrb organization(s): Jay Beaton Consulting LLC
maheshv
gurgolo
sundersingh18
efpapado organization(s): utdanning.no
mxr576
kfolsom
rosk0 organization(s): Catalyst IT
idebr organization(s): iO
markie organization(s): Interpersonal Frequency
ccarnnia
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.