Issue
Contribution records
Contributors

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

Give credit to everyone
Joram
jzavrl organization(s): NDP
darrenwh volunteering organization(s): Investis Digital
japerry organization(s): Acquia
hongpong volunteering organization(s): kor group
damienmckenna organization(s): Current
me5h
rvanderh1
mattlt
adriancid volunteering
dunebl
sneo
markpavlitski
joelpittet organization(s): The University of British Columbia
renrhaf organization(s): Skazy customer(s): OPT NC
suit4
thalles organization(s): CI&T
AnaSwin
eblue organization(s): Northern Commerce
t-lo volunteering
Christopher Riley
seros-me
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.