Contribution records
Contributors

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

Give credit to everyone
k_zoltan k_zoltan
coltrane coltrane
mihai_brb mihai_brb
yesct YesCT
grwgreg grwgreg
cyberschorsch Cyberschorsch
aiypz aiypz
alippai alippai
phiit phiit
dougvann dougvann
ZenDoodles ZenDoodles
eshta lkhaas
hrbel hrbel
amateescu amateescu
David_Rothstein drothstein
StuartJNCC StuartJNCC
sun sun
alimac alimac
deepakaryan1988 deepakaryan1988 organization(s): Material
dpi dpi volunteering
mohit1604 MohitMalik organization(s): Google Summer of Code
mcdruid mcdruid organization(s): Acquia
pdenooijer pdenooijer volunteering customer(s): RTL Nieuws, Sijthoff Media
davidwhthomas davidwhthomas
drumm drumm organization(s): Drupal Association
klausi klausi organization(s): jobiqo - job board technology
catch catch organization(s): Third and Grove
larowlan larowlan organization(s): PreviousNext
andypost andypost volunteering organization(s): Skilld
alexgreyhead alexharries
damien tournoud damz
rob c robc
star-szr star-szr volunteering
kim.pepper kimpepper organization(s): PreviousNext
Traverus mahon.mark
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.