Contribution records
Contributors

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

Give credit to everyone
just_like_good_vibes just_like_good_vibes volunteering
markhalliwell markcarver organization(s): Tag1 Consulting, Inc.
aaronbauman aaronbauman organization(s): Message Agency
vorapoap vorapoap volunteering
drugan drugan volunteering
gge gge
gdaw gdaw volunteering
jedgar1mx jedgar1mx
esteinborn esteinborn
strelkovandreyvalerievich strelkovandreyvalerievich
dudleyc dudleyc
xamount xamount volunteering
chri5tia chri5tia
kedarkhaire kedarkhaire volunteering
denix denix volunteering
danielveza DanielVeza organization(s): Sparks Interactive
upchuk Knob volunteering
xurizaemon xurizaemon
peetrovich peetrovich
anaconda777 anaconda777 volunteering
mchoffa mchoffa
jorgediazhav jorgediaz volunteering
gdev2018 gdev2018
asuresh asuresh
terminalc terminalc
bwoods bwoods volunteering
blur702 blur702
wahido mgaidi.wahid
kunal_singh kunal_singh
avo webworks avowebworks
nor sairi maxsim86 volunteering
lazar.lehel lazar.lehel
sajjad ali SajjadAli
Déjà vu shakyak volunteering
ashok.gharpankar ashok.gharpankar volunteering
joran lafleuriel ratjaune
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.