Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
breidert organization(s): 1xINTERNET
marcus_johansson organization(s): FreelyGive customer(s): Acquia
andypost volunteering organization(s): Skilld
bisonbleu volunteering
darren oh organization(s): Cognizant Softvision, Drupal Forge
matthews volunteering organization(s): amazee.io
lussoluca organization(s): SparkFabrik
rfay
dan2k3k4 organization(s): amazee.io customer(s): amazee.io
lpeabody volunteering organization(s): Digital Polygon
andrewbelcher organization(s): FreelyGive
moshe weitzman
robertoperuzzo organization(s): SparkFabrik
kristen pol organization(s): Itty Bitty Byte, Salsa Digital
nexusnovaz organization(s): Zoocha
littlepixiez
abhisekmazumdar organization(s): Dropsolid customer(s): Dropsolid
scott_euser volunteering organization(s): Soapbox
codebymikey organization(s): Zodiac Media
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.