Contribution records
Contributors

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

Give credit to everyone
heatherwoz heatherwoz
jvalencia jvalencia
mgifford mgifford organization(s): OpenConcept Consulting Inc.
ShareThis_Missy ShareThis_Missy
2dareis2do 2dareis2do
benjarlett benjarlett
gaxze GaxZE
dame dameert
eleuthere eleuthere
chartmann carey.hartmann
epringi epringi
bvoynick bvoynick
vinmassaro vinmassaro
yogeshmpawar yogeshmpawar organization(s): QED42
navneet0693 navneet0693 volunteering organization(s): QED42
naveenvalecha naveenvalecha volunteering organization(s): Acquia
johncionci johncionci organization(s): Oomph, Inc.
moghingold moghingold
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
Everett Zufelt everettz
Patrick Nelson TheWebmasterCentre
bart.hanssens bart.hanssens
stefan.r stefan.r
joseph.olstad joseph.olstad volunteering
ShareThis Support ShareThis_Support
will kirchheimer WillKirchheimer
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.