Contribution records
Contributors

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

Give credit to everyone
10basetom 10basetom
cstony0917 cstony0917
mjgruta mjgruta
betoscopio betoscopio
floown floown
dr1ss dr1ss
roam2345 jucallme
michaek michaek
gael_kl gael_kl
rolfmeijer rolfmeijer
korund korund
r8r8r r8r8r
develway develway
typoagrafka typoagrafka
devth8 devth8
nicholasthompson njt1982
uberblue gwillia8
batigol batigol
demoshane Demoshane
markiz markiz
hedac hedac
djschoone djschoone
marcoka eanima
wizonesolutions wizonesolutions
giorgio79 giorgio79
beto_beto beto_beto
haggins haggins
RavindraSingh it.ravindrasingh
rezarad rezarad
aufumy aufumy organization(s): Red Rocket Creative Strategies
sun-fire sun-fire
v.kopitsa v.kopitsa
kristen pol kepol
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.