Issue
Contribution records
Contributors

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

Give credit to everyone
chx
catch
yched
pasqualle
hypertext200
droplet
ParisLiakos
btmash volunteering
zhangtaihao
xjm
mlncn
radimklaska
5n00py
chanderbhushan
anton-staroverov
barry_fisher
dasjo
drupalhooked
wamilton
djdevin
attiks
Shellingfox
mgifford
jhedstrom organization(s): Phase2
davidsickmiller
cilefen
burkeker
ohthehugemanatee organization(s): Forum One
lesonunique
dinarcon organization(s): Agaric
andypost volunteering organization(s): Skilld
dgtlmoon
mustanggb
parasolx volunteering organization(s): Hadafi Solution & Resources
andyf organization(s): Fabb
poker10 organization(s): ActivIT s.r.o.
anrikun
fabianx organization(s): HeroDevs
mcdruid organization(s): Acquia
tim.plunkett
sylvain lecoy
Gnanasampandan Velmurgan volunteering
brad.bulger
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.