Issue
Contribution records
Contributors

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

Give credit to everyone
piyuesh23
argosbass
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
jibran
meramo
pec
pieterjanput organization(s): iO
chegor
VaithianathanV
ashutoshsngh organization(s): Material
disasm organization(s): AppliedTrust
cglewis07 volunteering
chuta
cilefen
JmOkay volunteering
lauriii organization(s): Druid
dman organization(s): Sparks Interactive
ameymudras volunteering
dawehner volunteering
xjm organization(s): Acquia
hugronaphor volunteering organization(s): Dennis customer(s): Dennis
mayurjadhav
marcelovani organization(s): Dennis
abhishek.kumar
nitesh pawar organization(s): Trigyn Technologies Ltd
scott weston
wuinfo - bill wu
sagar ramgade volunteering
trupti bhosale organization(s): Axelerant
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.