Contribution records
Draft
Contributors

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

Give credit to everyone
aspilicious aspilicious
klonos klonos
sinasalek sinasalek volunteering organization(s): Practicalidea
sourcesoft sourcesoft
xjm xjm
Gaelan Gaelan
marcingy marcingy
cweagans cweagans
bdgreen bdgreen
tstoeckler tstoeckler
starchild starchild
herom herom
hanno Hanno
fabianx Fabianx volunteering
David_Rothstein drothstein volunteering
bgilhome bgilhome
mustanggb akamustang
deviantintegral deviantintegral organization(s): Lullabot
catch catch organization(s): Third and Grove
hadi farnoud hadifarnoud volunteering
gábor hojtsy goba
tim.plunkett tim.plunkett
wuinfo - bill wu wuleinj
sepehr.sadatifar sepehrmm
dave reid davereid
stefan.r stefan.r
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.