Issue
Contribution records
Contributors

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

Give credit to everyone
vladimiraus organization(s): Tomato Elephant Studio
davesparks
gargsuchi organization(s): Salsa Digital
jannakha volunteering organization(s): Tomato Elephant Studio
larowlan organization(s): PreviousNext
p_stampy
pameeela
wiifm volunteering
fubarhouse organization(s): PreviousNext
acbramley organization(s): PreviousNext
jct321 volunteering organization(s): Morpht
nigelcunningham
mstrelan organization(s): PreviousNext
richo_au
jimmycann
marji organization(s): Morpht
murrayw organization(s): Morpht
danielveza organization(s): PreviousNext
dieuwe organization(s): Sparks Interactive
nick_schuch
akhil@salsa organization(s): Salsa Digital
josh waihi organization(s): Acquia
ivan zugec organization(s): WebWash
kim.pepper organization(s): PreviousNext
daynis-olman
mel.stubbings
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.