Contribution records
Contributors

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

Give credit to everyone
ChrisKennedy chriskennedy
drooppi drooppi
eaton eaton
Fayna Fayna
gausarts gausarts
cmarcera cmarcera
greggles greggles
dnewkerk Keyz
davedelong davedelong
snippa snippa
darumaki darumaki
domesticat domesticat
mryoung mryoung
skizzo skizzo
IngusNeilands IngusNeilands
tebb Dru-p
Magnity magnity
Toque Toque
drupaloSa drupalosa
marvix marvix
udvranto udvranto
ulf1 ulf1
Crell Crell
somerandomnerd somerandomnerd
robertdjung robertdjung
igorik igorik
kecinzer kecinzer
Nightroan Nightroan
nkraf nkraf
Marat Marat
loze loze
zilla zilla
Electronick Electronick
a_c_m acm
anarcat anarcat
eMPee584 empee584
omar patdam
anders.fajerson fajerstarter
Radiating Gnome Radiating_Gnome
skirr@drupal.ru skirr-at-drupal.ru
Flying Drupalist Flying_Drupalist
kyle.vh kyle.vh
bgibson-glu bgibson-glu
Petec-1 Petec-1
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.