Contribution records
Contributors

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

Give credit to everyone
francewhoa Francewhoa
catch catch
Bojhan bojhan
bleen bleen18
fabsor fabsor
webchick webchick
JeremyFrench JeremyFrench
janusman janusman
andypost andypost
lotyrin lotyrin
dejbar dejbar
mh86 mh86
colan colan
chx chx
fago fago
klausi klausi
tstoeckler tstoeckler
marcingy marcingy
jamonation jamonation
yhahn yhahn
phantomvish vishnuvijayan
alex_b alexb
sfinerty sfinerty
gianfrasoft gianfrasoft
yonailo yonailo
TCRobbert TCRobbert
wqmeng wqmeng
wojtha wojtha
dddave dddave
deviantintegral deviantintegral
gielfeldt gielfeldt
asb asb
gpk gpk
marthinal marthinal
seabear seabear
RAWDESK RAWDESK
moshe weitzman weitzman
sun.core sun.core
wim leers wimleers
alan d. aland
dave reid davereid
gábor hojtsy goba
vlad.dancer vlad.dancer organization(s): Drupalway
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.