Contribution records
Contributors

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

Give credit to everyone
benjy benjy organization(s): PreviousNext
heddn lucashedding organization(s): MTech, LLC
quietone quietone volunteering
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
xjm xjm organization(s): Acquia
fernandohv fernandohv
tbrameshbabu tbrameshbabu
deepakaryan1988 deepakaryan1988 organization(s): Therefore
hussainweb hussainweb organization(s): Axelerant
kurthill4 kurthill4
njim nJim
vegantriathlete vegantriathlete volunteering
vprocessor vprocessor organization(s): Skilld
mile23 Mile23 volunteering
mikeryan mikeryan organization(s): Virtuoso Performance
lars toomre ltoomre volunteering
jeffrey.vargas jvargas92 volunteering
The Sean The_Sean
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.