Contribution records
Draft
Contributors

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

Give credit to everyone
bowersox brandonojc
mgifford mgifford organization(s): OpenConcept Consulting Inc.
nevets nevets
franz franz
xano Xano
falcon03 falcon03
larowlan larowlan
pancho pancho
catch catch
webchick webchick
tstoeckler tstoeckler
yesct YesCT
Lowell Lowell
kattekrab kattekrab
manningpete manningpete
rpayanm rpayanm organization(s): SeeD EM
siva_epari siva-epari volunteering
andrewmacpherson andrewmacpherson volunteering organization(s): Annertech
damienmckenna damienmckenna organization(s): Current
smustgrave smustgrave organization(s): Mobomo
nicxvan nicxvan
Everett Zufelt everettz
steven jones darthsteven
tim.plunkett tim.plunkett organization(s): Acquia
les lim lesmana
kentr kentr volunteering
liam morland lkmorlan volunteering organization(s): OpenPlus, Scouting Waterloo Region
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.