Contribution records
Contributors

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

Give credit to everyone
peacog Peacog volunteering
smith76 Smith76
brunodbo brunodbo organization(s): Textillia
darrick darrick
hypertext200 heshanlk volunteering
daggerhart daggerhart volunteering
robpowell robpowell volunteering
brooke_heaton brooke_heaton
kclarkson kclarkson
bgilhome bgilhome
anybody Anybody
scottrigby scottrigby organization(s): NBCUniversal
caldenjacobs caldenjacobs
kris77 Kris77
zanvidmar zanvidmar volunteering
skdrupal88 ikorgik organization(s): SystemSeed customer(s): SystemSeed
willabby willabby
colan colan organization(s): Colan Schwartz Consulting, Consensus Enterprises
mortona2k mortona2k
liquidcms liquidcms
dqd dqd volunteering organization(s): MAROQQO studios
pasqualle pasqualle volunteering
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
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.