Issue
Contribution records
Contributors

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

Give credit to everyone
mikeytown2
mgifford organization(s): OpenConcept Consulting Inc.
playfulwolf
tstoeckler volunteering
joelpittet
penyaskito organization(s): Lingotek
yesct
fabianx volunteering organization(s): Tag1 Consulting, Inc.
jhedstrom
pendashteh
btopro organization(s): Pennsylvania State University
marcingy organization(s): Examiner.com
David_Rothstein volunteering
cilefen
jonhattan
catch
xjm organization(s): Acquia
stewsnooze volunteering
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
pounard
ndobromirov organization(s): JAKALA (formerly FFW)
pjcdawkins
FluxSauce organization(s): Four Kitchens customer(s): Meredith Corporation
joseph.olstad volunteering
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.