Issue
Contribution records
Contributors

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

Give credit to everyone
mradcliffe organization(s): Kosada
gnuget volunteering organization(s): Agaric
andypost volunteering organization(s): Skilld
daffie organization(s): Finalist
alphin organization(s): Valuebound
prabha1997 organization(s): Valuebound customer(s): Valuebound
sivaji_ganesh_jojodae volunteering
mindbet volunteering
ankithashetty volunteering organization(s): Specbee
alexpott organization(s): Acro Commerce, Thunder
darklight90
joshua1234511 organization(s): Salsa Digital
andregp organization(s): CI&T
arantxio organization(s): Finalist
mondrake volunteering
larowlan organization(s): PreviousNext
catch organization(s): Third and Grove
quietone organization(s): PreviousNext
boobaa organization(s): Pronovix
ravi.shankar organization(s): OpenSense Labs
sashi.kiran volunteering
rohan-sinha organization(s): Material
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.