Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
interlated volunteering
dileepkumargembali
shivam_tiwari organization(s): Innoraft
shashi_shekhar_18oct organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
blasoliva
ananya.k organization(s): Virasat Solutions
rakesh.nimje84@gmail.com
vivek panicker organization(s): Innoraft
stefan.korn organization(s): Stefan Korn - Webentwicklung
ksemihin
bmunslow
ryan-l-robinson
onfire84
naylor
aryan singh organization(s): Innoraft
vishal prasad
kiwad
mkhamash
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.