Contribution records
Contributors

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

Give credit to everyone
3rdLOF kannary
jzornig jzornig
cpelham cpelham
dixon_ dixon
Torenware torenware
heckad heckad
trangunghoa trangunghoa
bagpiper bagpiper
yannickoo yannickoo
csander csander
Citlalli Citlalli
jmonroe mtech
luistope luistope
kyke01 kyke01
Myoos Myoos
Seb36 Seb36
gregmarsh gregmarsh
timaholt trimsyndicate
roborracle roborracle
shrop shrop
kyleoliveira kyleoliveira
Exploratus Exploratus
Offlein Offlein
skwashd skwashd
windmaomao windmaomao
chrisjlee chrisjlee
ascii122 ascii122
pfrenssen pfrenssen
dgamache dgamache
kwfinken kwfinken
flashwebcenter flashwebcenter organization(s): Flash Web Center, LLC customer(s): Flash Web Center, LLC
David4514 David4514
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.