Contribution records
Draft
Contributors

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

Give credit to everyone
pwolanin pwolanin volunteering organization(s): SciShield
lauriii lauriii volunteering
catch catch organization(s): Third and Grove
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
frob frob organization(s): Clarity Innovations, Inc.
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
markhalliwell markcarver organization(s): Tag1 Consulting, Inc.
jwilson3 jwilson3 organization(s): Bluespark
diamondsea diamondsea volunteering organization(s): Publicis Sapient
gg4 double
chi Chi
fathershawn fathershawn organization(s): Digital Pulp
stephencamilo stvcomp volunteering
maacl maacl
xjm xjm organization(s): Acquia
larowlan larowlan organization(s): PreviousNext
dww dww organization(s): TEN7
smustgrave smustgrave organization(s): Mobomo
samuel.mortenson samuel.mortenson organization(s): Acquia
star-szr star-szr organization(s): Northern Commerce
elijah lynn ElijahLynn organization(s): Red Hat
geek-merlin geek-merlin organization(s): Geeks4Change, MachbarMacher
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.