Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
nod_ volunteering
pguillard
himanshupathak3 volunteering organization(s): Material
dawehner volunteering organization(s): Tag1 Consulting, Inc.
olli
borisson_ volunteering
mathysp organization(s): Mia Interactive
dgcollard
thatpatguy
jelle_s organization(s): Attiks
ashishdalvi organization(s): Blisstering Solutions
rasikap organization(s): Blisstering Solutions
droplet
ranaivo volunteering
impalash organization(s): Google Summer of Code
kreyol_dev volunteering
guypaddock organization(s): Inveniem
manjit.singh organization(s): Material
ankit agrawal volunteering
nileema.jadhav organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
igor.barato volunteering
nicobot
quietone organization(s): PreviousNext
kentr
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.