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 organization(s): Sparks Interactive
fubarhouse organization(s): PreviousNext
jannakha
jct321 volunteering
Richo
amberhenry
mattcommons organization(s): Morpht
mostrorec volunteering
sarwan_verma organization(s): Virasat Solutions
campbellt_ organization(s): Technocrat
cb organization(s): Morpht
febdao
fi_crowson
gargsuchi organization(s): Salsa Digital
griffynh
jonathan_hunt organization(s): Catalyst IT
lgreenshelley
owenlansbury organization(s): PreviousNext
akhil@salsa organization(s): Salsa Digital
ana.beltran
fonda-
jason.coghlan
andre.kakos organization(s): Morpht
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.