Issue
Contribution records
Contributors

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

Give credit to everyone
rhouse
paulgemini
pcambra
carn1x
rfay
Dryphtnet
AJen
dman
amaree
goodeit
Masala
PedroKTFC
dready2011
lwalley
hepabolu
summit
vinmassaro
mknet
seaneffel
twistor
megachriz volunteering organization(s): WebCoo
stevenkkim
drclaw
kenpeter
itamair
richsky
izus
ressa
runeasgar
chilligroup
st8ofmindz79
khumbu
mahmost
huijing
zmove
mslywka volunteering
ufku
impara
bneil organization(s): The University of Iowa
anas_maw organization(s): Vardot
cyclone321
firewaller
millionleaves volunteering
cgmonroe volunteering
azinck
nelslynn
helmo organization(s): Initfour websolutions customer(s): Aegir Cooperative
Collins405
justanothermark organization(s): CTI Digital
internal volunteering
haver
Helice volunteering
5n00py
manu manu
patrik.hultgren
alan d.
vincent rommelaars
stewart.adam
Christopher Riley
tyler-durden
scotthorn
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.