Contribution records
Contributors

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

Give credit to everyone
webchick webchick
eaton eaton
dries dries
quicksketch quicksketch
drewish drewish
dww dww
pancho pancho
robloach robloach
catch catch
greggles greggles
recidive recidive
alexanderpas alexanderpas
sun sun
chx chx
jrabeemer Giovanni_Glass
fago fago
PixelClever aaronhawkins
ccoletta ccoletta
arman arman
fractile81 fractile81
mitchell mitchell
dmitrig01 dmitrig01
avpaderno avpaderno
caktux caktux
matt2000 matt2000
robertdouglass robertDouglass
Bojhan bojhan
Frando frando
Crell Crell
yched yched
SeanBannister seanbannister
johnalbin johnalbin
nancydru nancyw
markus_petrux markuspetrux
guillaumeduveau guix
nicholasthompson njt1982
mcarbone mcarbone
drupal_was_my_past rocket
moshe weitzman weitzman
owen barton grugnog
paul.lovvik paullovvik
les lim lesmana
john morahan jmorahan
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.