Contribution records
Contributors

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

Give credit to everyone
khoogheem khoogheem
bessone bessone
hanskuiters HansKuiters
a_c_m acm
dunkoh dunkoh
hendryman hendryman
dgtlmoon dgtlmoon
andydragt andydragt
suoko suoko
henns20 henns20
johnvsc johnvsc
jasonwhat jasonwhat
mr_spark mr_spark
mediamash mediamash
sstacks sstacks
vegeneric vegeneric
k3vin k3vin_git
berty_boy berty_boy
mediahackers mediahackers
asak asak
ambiance7 ambiance7
bloke_zero bloke_zero
lelizondo lelizondo
pomliane Pomliane
s.daniel s.Daniel
chris.wells chris.wells
Damjan Dvorsek Damjan_Dvorsek
sukh.singh sukhjindersingh
Sangeetha-1 Sangeetha-1
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.