Contribution records
Contributors

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

Give credit to everyone
cucat cucat
webernet webernet
amaltheos amaltheos
petiar petiar
drewish drewish
rowdypostman rowdypostman
Benj Benj
drupalninja99 jaykali
fattmox fattmox
hypatia7777 hypatia7777
mrgoltra mrgoltra
scifisi scifisi
k74 k74
brazorf brazorf
giorgosk GiorgosK
tolland76 tolland76
merzikain merzikain
sunchaser sunchaser
Michali Michali
hanno Hanno
gvelez17 gvelez17
lolmaus lolmaus
Balbo Balbo
Dirk Dirk
valderama valderama
ericg ericg
ieyara ieyara
tinny tinny
jallenb jallenb
marazmus marazmus
agmin agmin
davestormuk davestormuk
gianfrasoft gianfrasoft
oferrero oferrero
aterchin aterchin
introfini introfini
mailfox mailfox
defconjuan defconjuan
Stan.Ezersky Stan.Ezersky
the-sandman the-sandman
Marko B MarkoBx
m.sant m.sant
drupal fan drupal_fan
reinderdevries@gmail.com reinderdevries-at-gmail.com
Todd Young ToddYoung
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.