Issue
Contribution records
Contributors

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

Give credit to everyone
5n00py volunteering
cilefen volunteering
hctom organization(s): undpaul
chipway organization(s): Chipway
rlhawk
andyg5000 organization(s): Blue Oak Interactive
mpolishchuck organization(s): Alpha Web Group customer(s): Dazzle
evilehk organization(s): Breakthrough Technologies, LLC customer(s): Breakthrough Technologies, LLC
fallenturtle
duaelfr volunteering organization(s): Happyculture
catch organization(s): Third and Grove
paulocs organization(s): CI&T
alexpott volunteering organization(s): Acro Commerce, Thunder
thalles organization(s): CI&T
berdir organization(s): MD Systems GmbH
pcambra organization(s): Cambrico customer(s): Farmier
sylus
quietone volunteering
wongjn volunteering
cdesautels
tim.plunkett organization(s): Acquia
ravi.shankar organization(s): OpenSense Labs
joseph.olstad
james.williams organization(s): ComputerMinds
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.