Contribution records
Contributors

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

Give credit to everyone
stella stella
szy szy
tic2000 tic2000
mrgoltra mrgoltra
davidwhthomas davidwhthomas
jcmarco jcmarco
adrinux adrinux
batbug2 batbug2
AlexisWilke alexiswilke
RobertPope RobertPope
sdrycroft sdrycroft
jdeg jdeg
baxr6 baxr6
mash200 mash200
andrewmacpherson andrewmacpherson
macmladen MacMladen
nyleve101 nyleve101
bendiy bendiy
not_Dries_Buytaert not_Dries_Buytaert
miro_dietiker mirodietiker
harryadu harryadu
modctek modctek
ani7a ani7a
raven_web raven_web
thinkpadius thinkpadius
jacobmn jacobmn
geerlingguy geerlingguy
asb asb
drjonez drjonez
gpk gpk
brayo4 brayo4
shane birley shanebirley
Nick Robillard nickel
open social goalgorilla
lwanga.matovu toviellesse
Jerome F Jerome F
bricef bricef
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.