Issue
Contribution records
Contributors

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

Give credit to everyone
donquixote
EvanDonovan
Frando
chx
jmpalomar
figaro
newbuntu
ShutterFreak
acrollet
nofuseto
sun
markus_petrux
picardo
oriol_e9g
mrfelton
catch
pwolanin volunteering organization(s): Acquia
mikeytown2
rmjiv
domidc
thebuckst0p
crea
bjcool
chrism2671
sinasalek
javiarauz
jannalexx
thekevinday
jhm
digi24
kenorb
gooddesignusa
alfthecat
asb
ericclaeren
AntiNSA
paganwinter
xjm
aspedia
vordude
bleen
ohnobinki
drupalninja99
j0rd
aLearningGuy
urlisse
danblack
fabianx volunteering organization(s): Tag1 Consulting, Inc.
attiks organization(s): Attiks
Mithrandir
damien tournoud
moshe weitzman
dyke it
Xinglin Zhang
aleksey.tk
andrew answer
Peter Bowey
sachin.bansal
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.