Issue
Contribution records
Contributors

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

Give credit to everyone
kscheirer
greggles
MichaelCole
matiaslezin
robloach
jhodgdon
firelf
ianthomas_uk
welly
alberto56
cs_shadow
loudmu
pimok3000
stuzog
jaypan
treksler
mrconnerton
jroberts
medienverbinder
damienmckenna organization(s): Current
kwerey
bdupls
wiifm volunteering organization(s): Acquia
juampynr organization(s): Lullabot
stevo70
ronaldmulero customer(s): edX
budda organization(s): Ixis - UK Drupal Support, Maintenance, Hosting and Development
adamps organization(s): AlbanyWeb
deetergp organization(s): Classic Graphics
xano organization(s): Druid
howards
joelpittet
hkirsman
tjcvd
damien tournoud
devin carlson
kaizerking
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.