Contribution records
Contributors

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

Give credit to everyone
tinto Tinto organization(s): The Savvy Few
uqjhawk3 uqjhawk3
danielveza DanielVeza volunteering organization(s): PreviousNext
mstrelan mstrelan organization(s): PreviousNext
ainsofs ainsofs
darvanen Darvanen
griffynh griffynh
tinarey RaspberryBlack
smustgrave smustgrave organization(s): Mobomo
larowlan larowlan organization(s): PreviousNext
amber himes matz amberhimesmatz organization(s): Drupalize.Me
kristen pol kepol organization(s): Itty Bitty Byte customer(s): OPTASY, Salsa Digital
jaime@gingerrobot.com jaimekristene organization(s): Ginger Robot
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.