Issue
Contribution records
Contributors

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

Give credit to everyone
eclipsegc
fago
xjm organization(s): Acquia
jibran volunteering organization(s): PreviousNext customer(s): University of Technology, Sydney
catch volunteering
tedbow volunteering organization(s): Acquia
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
tstoeckler volunteering
berdir organization(s): MD Systems GmbH
andypost volunteering organization(s): Skilld
larowlan organization(s): PreviousNext
anybody
alexpott organization(s): Thunder
seanb
joelpittet organization(s): The University of British Columbia
hugronaphor volunteering organization(s): Acrosto customer(s): manifesto
beanjammin organization(s): Domain7
nikitagupta organization(s): Material customer(s): Drupal India Association
joegraduate organization(s): The University of Arizona
renatog organization(s): CI&T
jeroent organization(s): iO
ankithashetty volunteering organization(s): Specbee customer(s): Drupal India Association
meenakshi_j organization(s): Material customer(s): Drupal India Association
paulocs organization(s): CI&T
tim.plunkett organization(s): Acquia
chr.fritsch organization(s): Thunder
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.