Contribution records
Draft
Contributors

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

Give credit to everyone
rszrama rszrama
julia_g julia_g
neopoet neopoet
liliplanet Liliplanet
mariuss mariuss
tjjacobsen tjjacobsen
Chad_Dupuis Chad_Dupuis
hefox hefox
BenK benk
darsic darsic
tr tr
fidlertom fidlertom
Rhino Rhino
hawkdrupal hawkdrupal
gpiersol gpiersol
scotwith1t phrancescot
dafeder dafeder
interestingaftermath interestingaftermath
RedBob62 RedBob62
francismacomber francismacomber
clr123 clr123
odisey odisey
webservant316 webservant316
timb timb
jukka792 jukka792
hejeva hejeva
jsibley jsibley
dzepol dzepol
ydahi ydahi
BenIPAQ BenIPAQ
aniebel aniebel
bachbach bachbach
SeanA SeanA
bisonbleu bisonbleu volunteering
eric.chenchao cityreader
texas-bronius bronius
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.