Issue
Contribution records
Contributors

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

Give credit to everyone
kjay
ifrik
yesct
yoroy organization(s): Roy Scholten
smaz organization(s): Five Mile Media
tkoleary organization(s): Acquia
andread
marameodesign organization(s): Marameo Design
tomatkins volunteering
lauriii organization(s): Druid
adamjuran organization(s): Forum One
wturrell volunteering
tameeshb organization(s): Google Summer of Code
tarekdj volunteering
ckrina organization(s): Ymbra
pk188 organization(s): OpenSense Labs
markhalliwell organization(s): Tag1 Consulting, Inc.
jofitz organization(s): ComputerMinds
djamdev
alexrayu volunteering
longwave organization(s): Full Fat Things
roberttabigue organization(s): Promet Source
avpaderno volunteering
gábor hojtsy organization(s): Acquia
manuel garcia volunteering organization(s): Appnovation
priyanka.sahni organization(s): Material customer(s): Drupal India Association
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.