Issue
Contribution records
Contributors

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

Give credit to everyone
Piegefull organization(s): Smile
grimreaper organization(s): Smile
timwood
alison volunteering
brucedarby organization(s): The University of Edinburgh
scuba_fly organization(s): ronder
jwlockhart organization(s): The University of Edinburgh
rachel_norfolk organization(s): Drupal Association
elachlan
andreyjan organization(s): JAKALA (formerly FFW)
rahulrasgon organization(s): QED42
edwardchiapet
prudloff organization(s): Insite
jenlampton organization(s): Jeneration Web Development customer(s): Backdrop CMS, Metropolitan Transportation Commission, Peak Digital, LLC
douggreen organization(s): Peak Digital, LLC
smustgrave organization(s): Mobomo
penyaskito organization(s): Lullabot
wendymc
petr illek volunteering organization(s): Annertech
neslee canil pinto organization(s): Specbee
sahana _n organization(s): Specbee
suresh prabhu parkala organization(s): Specbee
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.