Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
kristen pol organization(s): Itty Bitty Byte, Salsa Digital
jjchinquist organization(s): drunomics, Drupal Austria
breidert organization(s): 1xINTERNET
scott falconer organization(s): Acquia
wouters_f organization(s): Dropsolid
nielsaers organization(s): Dropsolid
guptahemant volunteering organization(s): QED42
marcus_johansson organization(s): FreelyGive
a.dmitriiev organization(s): 1xINTERNET
pedrop organization(s): Brainsum
fago organization(s): drunomics
matthews volunteering organization(s): amazee.io, James Matthew Saunders LLC
bbruno organization(s): 1xINTERNET
afoster organization(s): Foster Interactive Inc.
anand.toshniwal93 volunteering organization(s): QED42
danrod volunteering organization(s): OPTASY
yautja_cetanu organization(s): FreelyGive
pdjohnson organization(s): 1xINTERNET
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.