Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
Asif99
newbuntu
Apollo610
fmueller
ratinakage
andypost volunteering organization(s): Skilld
sbefort
johnbarclay
drtrueblue
jyotisankar
cilefen
adewinne organization(s): Therefore
m0ray79
jonathanshaw
sandeep_jangra
quietone organization(s): PreviousNext
dww organization(s): 3281d Consulting customer(s): SMAI
-Anti-
Dave Cohen
moshe weitzman
debra-v
sadanand kenganal
geek-merlin organization(s): Geeks4Change, MachbarMacher
Git commit message
Commit types
  • 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

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.