Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
hideaway
blacklabel_tom organization(s): Reason Digital
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
cms_macgyver volunteering
slucero organization(s): Current
rbayliss organization(s): Last Call Media customer(s): Commonwealth of Massachusetts
daffie
bvoynick organization(s): Interactive Strategies
nicxvan
andypost volunteering organization(s): Skilld
john cook organization(s): Creode
y.sa
m4olivei
oily
dries
nod_ organization(s): Très Bien Tech customer(s): Palantir.net, Vardot, Sprintive
alexpott organization(s): Acro Commerce, Thunder
smustgrave organization(s): Mobomo
sakshi@17
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.