Contribution records
Draft
Contributors

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

Give credit to everyone
mparker17 mparker17 organization(s): Cool Blue Interactive
pancho pancho volunteering
w01f W01F
colan colan organization(s): Colan Schwartz Consulting, Consensus Enterprises
dww dww volunteering
bdimaggio bdimaggio
dkosbob dkosbob organization(s): Message Agency
pasqualle pasqualle volunteering
tijsdeboeck tijsdeboeck organization(s): Open Up Media
adaddinsane adaddinsane volunteering
adriancid adriancid volunteering organization(s): Drupiter
jonmcl JonMcL
joegraduate joegraduate organization(s): The University of Arizona
daniel-san daniel-san
peter caritas PeterCaritas
orkutmuratyilmaz orkut
liam morland lkmorlan organization(s): OpenPlus, Scouting Waterloo Region
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.