Issue
Contribution records
Contributors

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

Give credit to everyone
switzern organization(s): Elevated Third
megachriz volunteering organization(s): WebCoo
amykhailova
dbungard organization(s): Kanopi Studios
irinaz volunteering organization(s): Fibonacci Web Studio
joecrespo
mandclu organization(s): Northern Commerce
meghancraft
skessler
sugaroverflow
volkswagenchick organization(s): Kanopi Studios
andrew_mallis organization(s): Kalamuna
jenlampton organization(s): Jeneration Web Development customer(s): Metropolitan Transportation Commission
kclarkson organization(s): Blend Me, Inc
michaelablackham organization(s): Aten Design Group
rachel_norfolk organization(s): Drupal Association
August1914
chicagomom volunteering
jrockowitz volunteering organization(s): The Big Blue House
mohit_aghera volunteering organization(s): Axelerant
njim organization(s): Four Kitchens
owenpm3 organization(s): Mobomo
chris burge organization(s): University of Nebraska
gábor hojtsy organization(s): Acquia
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.