Contribution records
Contributors

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

Give credit to everyone
ckrina ckrina organization(s): Lullabot
aaronmchale AaronMcHale organization(s): The University of Edinburgh
amourow amouro volunteering
anushrikumari anushri19 organization(s): OpenSense Labs customer(s): Drupal Association
dunx dunx organization(s): CACI Digital Experience (formerly Cyber-Duck)
NikMis NikMis
outi Outi organization(s): Mearra (formerly known as Wunder)
prudloff prudloff organization(s): Insite
the_g_bomb the_g_bomb organization(s): CACI Digital Experience (formerly Cyber-Duck)
emma horrell emma-horrell organization(s): The University of Edinburgh
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.