Issue
Contribution records
Contributors

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

Give credit to everyone
googletorp volunteering organization(s): Reveal IT
karens organization(s): Lullabot
svendecabooter volunteering organization(s): Sven Decabooter
benjy organization(s): PreviousNext
quietone volunteering
spokje volunteering
neograph734 volunteering
tregonia organization(s): Parallax Information Technology
generalredneck
hussainweb organization(s): Axelerant
jeffwpetersen
xmacinfo
catch organization(s): Third and Grove
mvdve
xjm organization(s): Acquia
phenaproxima organization(s): Acquia
attheshow
mikeryan volunteering organization(s): Virtuoso Performance
whop
steinmb volunteering
imiksu volunteering organization(s): Mearra (formerly known as Wunder)
brunodbo organization(s): Textillia
joelpittet organization(s): The University of British Columbia
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.