Issue
Contribution records
Contributors

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

Give credit to everyone
Max1
derekw
katannshaw
mparker17 organization(s): OpenConcept Consulting Inc.
dsdeiz organization(s): Promet Source
sagannotcarl volunteering
bmateus
istryker
nicrodgers
ninabyte
ckellyirish
captainack
jenlampton volunteering organization(s): Jeneration Web Development customer(s): Metropolitan Transportation Commission
anpolimus volunteering organization(s): Drupal Ukraine Community
alansaunders92
jshosseini
akolahi
trumanru
damienmckenna organization(s): Current
wylbur organization(s): Electric Citizen
ashzade volunteering
Michele Wickham
vishal.sheladiya volunteering
alex awg 2015 organization(s): Drupal Ukraine Community
vali hutchison
liam morland organization(s): University of Waterloo
chris matthews volunteering
brad.bulger
cameron prince
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.