Contribution records
Contributors

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

Give credit to everyone
joachim joachim
yched yched
xjm xjm
Bojhan bojhan
gaas gisle
kid_icarus kid_icarus
kbk kbk
yesct YesCT
rkjha rkjha
disasm disasm
zetagraph zetagraph
attiks attiks
shariharan subru77
kshama_deshmukh kshama_deshmukh
akozma akozma
swentel swentel
miniwebs2 kaybee57
catch catch
klonos klonos
sutharsan sutharsan
dcam dcam
mgifford mgifford
deanflory deanflory
David_Rothstein drothstein
sassafrass synsas volunteering
cilefen cilefen
andrewtur atur
shobhit_juyal shobhit_juyal volunteering organization(s): Material
quietone quietone volunteering
star-szr star-szr
praveen kumar r praveen_kumar_R organization(s): DrupalPartners
mbutcher mbutcher
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.