Contribution records
Contributors

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

Give credit to everyone
infojunkie kratib
jcontreras jcontreras78 organization(s): Texas Creative
pday pday
sirclickalot SirClickALot
adam1 adam1 volunteering
raveen_thakur51 raveeny volunteering organization(s): LN Webworks Private Limited customer(s): LN Webworks Private Limited
tikaszvince tikaszvince organization(s): Integral Vision Ltd
berdir berdir organization(s): MD Systems GmbH
maxilein maxilein
phjou stargayte
bsnodgrass bsnodgrass organization(s): net2Community, Inc.
nicoleannevella nicoleannevella volunteering
dydave DYdave organization(s): Code Enigma
trickfun trickfun
tonytheferg TonyTheFerg
mihaic mihaic volunteering organization(s): United Nations
drewcking drewcking organization(s): Cyberwoven
uv516 Uv516 volunteering
ericgsmith ericgsmith
ressa ressa organization(s): Ardea
bwoods bwoods organization(s): University of Maryland
yesct YesCT organization(s): Lullabot customer(s): The Michael J. Fox Foundation for Parkinson's Research
keshav patel Keshav organization(s): Dassault Systèmes
kevin.pfeifer kevin.pfeifer
anandaakrishnan-ga Anandaakrishnan_GA volunteering
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.