Issue
Contribution records
Contributors

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

Give credit to everyone
slootjes
Munavijayalakshmi organization(s): Valuebound
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
abhishek_10 organization(s): OpenSense Labs
alexpott volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
anemes organization(s): PitechPlus
mpdonadio organization(s): DiD Agency
prash_98 organization(s): Google Summer of Code
borisson_ volunteering organization(s): Calibrate
tanubansal organization(s): Salsa Digital
quietone volunteering organization(s): PreviousNext
darvanen
johnalbin organization(s): Annertech
catch organization(s): Third and Grove
spokje
gaurav.kapoor organization(s): OpenSense Labs
himanshu-dixit volunteering
shubham.prakash organization(s): OpenSense Labs
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.