Issue
Contribution records
Contributors

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

Give credit to everyone
Pierrere volunteering
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
jamesliu78
dineshw volunteering organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
ajithams_zyxware organization(s): Zyxware Technologies
dagmar organization(s): Globant
dileepmaurya
stomusic
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
charginghawk organization(s): Genuine
yogeshmpawar organization(s): QED42
Anyeos volunteering
idebr organization(s): ezCompany, iO
nicrodgers organization(s): Welsh Government
BartNijs
igorski volunteering
berdir
mpdonadio organization(s): DiD Agency
cestmoi
redseujac volunteering
scott_euser volunteering organization(s): Soapbox
mpp organization(s): AmeXio Fuse customer(s): District09
larowlan organization(s): PreviousNext
topology
Coops_ volunteering
dgaspara organization(s): NTT DATA
mohit_aghera volunteering organization(s): QED42
lendude organization(s): iO
xdong
darius.restivan volunteering
gaurav.kapoor organization(s): OpenSense Labs
dom. volunteering organization(s): ACINO
manuel.adan organization(s): Arcovía Digital
wim leers
abdelrahman amer organization(s): Vardot
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.