Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
kmoll organization(s): Appnovation customer(s): Pfizer, Inc.
m4olivei organization(s): Lullabot
mustanggb
deviantintegral organization(s): Lullabot
nuez
dieterholvoet organization(s): Wieni
codebymikey organization(s): Zodiac Media
tibezh volunteering organization(s): Drupal Ukraine Community
mile23 volunteering organization(s): CivicActions
_utsavsharma organization(s): OpenSense Labs customer(s): DrupalFit
jastraat organization(s): CivicActions
neclimdul organization(s): APQC
intrafusion organization(s): Cambridge Audio
swirt organization(s): CivicActions customer(s): Centers for Medicare and Medicaid Services
bapplejax organization(s): MetroStar Systems customer(s): Department of Veterans Affairs
chri5tia organization(s): CivicActions customer(s): Department of Veterans Affairs
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
nick.murza volunteering organization(s): Indrivo
moshe weitzman
gun_dose volunteering organization(s): Your Dev Team
skyriter organization(s): CivicActions customer(s): Department of Veterans Affairs
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.