Issue
Contribution records
Contributors

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

Give credit to everyone
ambientdrup
u4yk
mohirt
katbailey
jangolden
arbel
mattcasey
christian_m
Macronomicus
devkinetic
wiliam_steven
elektrorl
Pocketpain
alanpeart
giorgio79
whatsupdrew
sunland
hexabinaer
ayesh
zkrebs
Chasen
PixelClever
chi
zrodimel
justkristin
JohnnyW
castawaybcn
tmsss
q11q11
rv0
calefilm
Bernsch
amanire
Exploratus
kenpeter
ultimateboy
cafuego
heresh
idcm
simone960
zuruckzugehen
arodriguezju
Eranga
AgentJay volunteering
thommyboy
sardis organization(s): Drupal Ukraine Community, Drupalway customer(s): Drupal Ukraine Community, Drupalway
nwom
millionleaves volunteering
karivolas
shelane
kim.le
randa.elayan
Binu Varghese
alain dg
lachezar.valchev volunteering
nitesh sethia volunteering organization(s): QED42
Gnanasampandan Velmurgan volunteering
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.