Issue
Contribution records
Contributors

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

Give credit to everyone
catch organization(s): Tag1 Consulting, Inc.
gábor hojtsy organization(s): Acquia
moshe weitzman
deviantintegral
longwave organization(s): Full Fat Things
joelpittet organization(s): The University of British Columbia
godotislate volunteering
borisson_ organization(s): Calibrate customer(s): Acerta
ressa
xjm organization(s): Zoocha, xjm
prudloff organization(s): Insite
solideogloria
cmlara volunteering organization(s): DM13 Security LLC
phenaproxima organization(s): Acquia
steven jones organization(s): ComputerMinds
jurgenhaas organization(s): LakeDrops
nicxvan organization(s): nLightened Development LLC
lambert
benjifisher volunteering organization(s): Harvard Web Publishing
quietone organization(s): PreviousNext
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.