Contribution records
Contributors

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

Give credit to everyone
giorgosk GiorgosK
ufku ufku
orchard orchard
ryanmargheriti ryanmargheriti
cwaxwing cwaxwing
seanhellwig seanhellwig
Foonaka Foonaka
bluefoot bluefoot
mpotter mpotter
litmusdesigns litmusdesigns
aviddv1 aviddv1
marianoog marianoog
criscom criscom
treehacker treehacker
genemachine genemachine
johnTEN johnTEN
generalconsensus generalconsensus
theoracleprodigy theoracleprodigy
ytsurk ytsurk
allan1015 allan1015
DeNelo DeNelo
smorrish smorrish
nancydru nancyw
den33775 den33775
sunchaser sunchaser
rsvelko rsvelko
mallin mallin
mollybee mollybee
deggertsen deggertsen
vaccinemedia vaccinemedia
SamSteinig SamSteinig
skrobe skrobe
colorsand colorsand
Sigvard Sigvard
thalles thallesvf organization(s): CI&T
WeRockYourWeb.com WeRockYourWeb.com
Störtebeker Stoertebeker
norwegian.blue norwegianblue-nz
jeroenwillemsen2001 jeroenwillemsen2001
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.