Issue
Contribution records
Contributors

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

Give credit to everyone
larowlan organization(s): PreviousNext
mikelutz volunteering organization(s): Four Kitchens
danielveza organization(s): Sparks Interactive
Pratik
acbramley organization(s): PreviousNext customer(s): Service NSW
amjad1233 volunteering
dipakmdhrm volunteering organization(s): QED42 customer(s): Drupal India Association
griffynh organization(s): PreviousNext
jibran organization(s): PreviousNext
jungle volunteering
naresh
Mixologic organization(s): Drupal Association
alexpott organization(s): Acro Commerce, Thunder
catch organization(s): Third and Grove
dawehner volunteering
dww volunteering
heddn organization(s): MTech, LLC
pameeela
quietone volunteering
shaal volunteering organization(s): Palantir.net
thursday_bw volunteering
xjm organization(s): Acquia
pratik_kamble organization(s): QED42
kristydv
Mustafa-1
surabhi-gokte volunteering organization(s): Material customer(s): Drupal India Association
pankaj.singh volunteering organization(s): Material customer(s): Drupal India Association
kristen pol organization(s): Hook 42
kim.pepper organization(s): PreviousNext
g-brodiei volunteering
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.