Contribution records
Contributors

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

Give credit to everyone
greggles greggles
bomarmonk bomarmonk
Moonshine moonshine
jordanlewin jordanlewin
TUc TUc
jesss jesss
hamoo hamoo
ramper ramper
choster choster
karens karens
greenskin greenskin
ellanylea ellanylea
Poieo Poieo
willvincent tcindie
beyond67 beyond67
domesticat domesticat
redndahead redndahead
isaac77 isaac77
tauno tauno
will_in_wi willinwi
mkrakowiak mkrakowiak
patcon patcon
designerbrent designerbrent
traviscarden TravisCarden
jhedstrom jhedstrom
stacysimpson stacysimpson
joelstein joelstein
jastraat jastraat
s4j4n s4j4n
mattbk mattbk
arlinsandbulte arlinsandbulte
c4rl c4rl
aren cambre arencambre
kars-t karst
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.