Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
webchick volunteering
zorz organization(s): Point Blank
yautja_cetanu organization(s): FreelyGive
scott falconer organization(s): Acquia
ronaldtebrake volunteering organization(s): Open Social
kristen pol organization(s): Itty Bitty Byte, Salsa Digital
marcus_johansson organization(s): FreelyGive
gábor hojtsy organization(s): Acquia
the_g_bomb organization(s): The University of Edinburgh
tonypaulbarker organization(s): Annertech customer(s): LocalGov Drupal
afoster organization(s): Foster Interactive Inc.
yesct organization(s): Lullabot customer(s): State of Georgia, The Michael J. Fox Foundation for Parkinson's Research
e0ipso volunteering customer(s): Acquia
emmasanders
ckrina organization(s): Cambrico
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.