Issue
Contribution records
Contributors

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

Give credit to everyone
jensimmons
jbrown
aspilicious
mustanggb
eric_a
TimG1
johsw
geerlingguy
Fidelix
dropbydrop
pillarsdotnet
fabianx
RobW
adamgerthel
quicksketch
mattjacobson
slackrunner
visualfox
catch
adamdicarlo
bt82
OnkelTem
jarrodirwin
drupal_was_my_past
jamesbenison
idflood
Bikkne
aeroweb340
crashtest_
webchick
klonos organization(s): Salsa Digital
btmash
tr
chx
pasqualle
marcingy
xjm
elc
aklys
kolafson
m4xjb
johnnynia
khiminrm
syodash
johnathankent
mikey_p
dave reid
Jeff Burnz
damien tournoud
lars toomre
sylvain lecoy
scott.whittaker
Dean Reilly
Tor Arne Thune
michael_lessard_micles.biz
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.