Issue
Contribution records
Contributors

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

Give credit to everyone
bolind
seanr
dpolant
Amarjit
kiwimind
abaier
enemyeye
gumpo
pomliane
mattm007
jras
bmx269
Dennis82
che8
thomaschall
jim22
mjcarter
andyg5000
drasgardian
rszrama
vladsh
jerryitt
thatoneguy volunteering
bradsmithcpa
boum148
kaldimar
robgreeniowa
olliebourne
summit
quardz
jgilberAZ
realobiwankenobi
benjarlett
rphillipsfeynman
vivianspencer
chrisfromredfin organization(s): Redfin Solutions, LLC
discipolo
jmary
kopeboy
stevieb
FrancescoUK
NeuQuest
technotim2010 volunteering
hadsie
kentjames1980
AntiNSA
shaxa organization(s): Bulcode
nelslynn
nhck
rmathew
Amberdine customer(s): Locus Publications
gmaximus
dvtalk
vadim.eremeev
As If
tomtech organization(s): Centarro
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.