Issue
Contribution records
Contributors

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

Give credit to everyone
samc
adrian
chx
nedjo
neclimdul
bomarmonk
webchick
ilmaestro
jakeg
celstonvml
quicksketch
yonailo
drewish
sreynen
bryancasler
vectoroc
kleinmp
marcingy
catch
fromtheindia
kscheirer
rudiedirkx
mvonfrie
kapilv volunteering
larowlan organization(s): PreviousNext
quietone volunteering organization(s): PreviousNext
lendude organization(s): iO
paulocs organization(s): CI&T
kattekrab organization(s): Red Hat
mikeryan organization(s): Tag1 Consulting, Inc.
Mir4 volunteering
s3b0un3t volunteering
thidd volunteering
smustgrave organization(s): Mobomo
alexpott organization(s): Acro Commerce, Thunder
papagrande organization(s): VTP Ventures
codebymikey organization(s): Zodiac Media
yovince
killes@www.drop.org
Bèr Kessels
moshe weitzman
damien tournoud
dave reid
kim.pepper organization(s): PreviousNext
ravi.shankar organization(s): OpenSense Labs
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.