Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
lostcarpark volunteering
igorgoncalves organization(s): ImageX
rodrigoaguilera volunteering
tmarkie
mradcliffe
john cook organization(s): Cojolan, Annertech
volkswagenchick volunteering
darren oh organization(s): Drupal Forge, Cognizant Technology Solutions customer(s): Estée Lauder Companies
salimlakhani volunteering organization(s): Drupal Forge
dinarcon organization(s): Agaric
greggmarshall volunteering organization(s): Vendor-Tech, Inc.
alvarito75 volunteering organization(s): Cochasoft
Amarshall
rfay organization(s): DDEV
kristen pol organization(s): Itty Bitty Byte, Salsa Digital
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
antojose
chrisdarke volunteering organization(s): MindAtomic
markie organization(s): Interpersonal Frequency
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.