Issue
Contribution records
Contributors

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

Give credit to everyone
znerol
daletrexel volunteering organization(s): University of Minnesota
gdemet organization(s): Palantir.net
pcambra organization(s): Cambrico
fholldorff organization(s): erdfisch
jpoesen organization(s): TrainingCloud
philipnorton42 volunteering
socketwench
c0debabe
johne volunteering
kreynen organization(s): University of Denver
mediaformat
fodaveg
mlncn organization(s): Agaric customer(s): Drutopia, Portside, Teachers with GUTS
mikemccaffrey
jr_kthor organization(s): Drupal Association
jeni_dc
neurer volunteering
greggles
volkswagenchick volunteering
ryan_witcombe organization(s): Drupal Association
greg.harvey organization(s): Code Enigma
andy-blum volunteering
reuben walker volunteering
gábor hojtsy organization(s): Acquia
back-2-95
darren oh organization(s): Cognizant Softvision
ghost of drupal past
drumm organization(s): Drupal Association
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.