Issue
Contribution records
Contributors

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

Give credit to everyone
Mixologic organization(s): Drupal Association
vladimiraus organization(s): Tomato Elephant Studio
hestenet organization(s): Drupal Association
shaal volunteering organization(s): Palantir.net
tdnshah volunteering organization(s): Material customer(s): Drupal India Association
tedbow organization(s): Acquia
xjm organization(s): Acquia
andypost volunteering customer(s): Skilld
atul4drupal
baddysonja organization(s): 1xINTERNET
catch organization(s): Third and Grove
dan2k3k4 organization(s): Amazee Labs
drumm organization(s): Drupal Association
dww volunteering
jungle volunteering
larowlan organization(s): PreviousNext
nerdstein volunteering
vuil organization(s): JAKALA (formerly FFW)
pingwin4eg volunteering organization(s): Drupal Ukraine Community
gábor hojtsy organization(s): Acquia
Nitesh-1
surabhi-gokte volunteering organization(s): Material customer(s): Drupal India Association
jyotimishra-developer organization(s): Material customer(s): Drupal India Association
kristen pol organization(s): Hook 42
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.