Issue
Contribution records
Contributors

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

Give credit to everyone
bradjones1 volunteering organization(s): Big Island Fish, Not Vanilla, Inc.
avpaderno volunteering
matt_paz
tipit volunteering organization(s): TIP Solutions
nigelcunningham organization(s): Technocrat
ridhimaabrol24 organization(s): Material customer(s): Drupal India Association
rajandro volunteering organization(s): Material customer(s): Drupal India Association
josephdpurcell organization(s): Bounteous
crasx organization(s): Bounteous
nickmans organization(s): The Reference
benjifisher organization(s): FRUITION
jhedstrom organization(s): Phase2
longwave organization(s): Full Fat Things
andregp organization(s): CI&T
giuseppe87
bbrala volunteering organization(s): SWIS
catch organization(s): Third and Grove
kingdutch organization(s): Open Social
marcofernandes organization(s): Frontkom
wim leers organization(s): Acquia
ravi.shankar organization(s): OpenSense Labs
tim.plunkett organization(s): Acquia
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
joseph.olstad
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.