Contributors

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

Give credit to everyone
mradcliffe mradcliffe organization(s): Kosada
chrisdarke ChrisDarke organization(s): MindAtomic
alison alison volunteering
alvarito75 alvarito75 volunteering organization(s): Cochasoft
Amarshall Amarshall volunteering
greggmarshall greggmarshall volunteering
hestenet hestenet organization(s): Drupal Association
igorgoncalves igorgoncalves volunteering organization(s): ImageX
lostcarpark lostcarpark
markie markie volunteering
mharrell mharrell
ninelivesblackcat NineLivesBlackCat volunteering
realityloop realityloop volunteering organization(s): Realityloop
rfay rfay organization(s): DDEV
ultimike ultimike organization(s): DrupalEasy
volkswagenchick volkswagenchick organization(s): The Linux Foundation
xjkwak xjkwak volunteering
yesct YesCT organization(s): Lullabot
anicoto anicoto organization(s): Cellar Door
darren oh darrenoh organization(s): Drupal Forge
kristen pol kepol organization(s): Salsa Digital, QuantCDN
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.