Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
dixon_ organization(s): Pfizer, Inc. customer(s): Pfizer, Inc.
amateescu customer(s): Pfizer, Inc.
hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
timmillwood organization(s): Pfizer, Inc.
effulgentsia organization(s): Acquia
sam152 volunteering organization(s): PreviousNext
plach volunteering customer(s): Acquia
pancho volunteering
berdir organization(s): MD Systems GmbH
catch organization(s): Third and Grove
larowlan volunteering
rakesh_verma volunteering customer(s): Google Summer of Code
tstoeckler
alexpott organization(s): Acro Commerce, Thunder
xjm
bbrala organization(s): SWIS
wim leers organization(s): Acquia
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.