Issue
Contribution records
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.
berdir organization(s): MD Systems GmbH
amateescu volunteering customer(s): Pfizer, Inc., Tag1 Consulting, Inc.
alexpott organization(s): Thunder
larowlan organization(s): PreviousNext
jeqq customer(s): Pfizer, Inc.
idebr organization(s): iO
pmelab organization(s): Amazee Labs
catch organization(s): Third and Grove
anushrikumari organization(s): OpenSense Labs
adityasingh volunteering organization(s): Material customer(s): Drupal India Association
atul4drupal
fabianx organization(s): Tag1 Consulting, Inc.
s_leu organization(s): Tag1 Consulting, Inc.
dspachos volunteering
smustgrave organization(s): Mobomo
gábor hojtsy organization(s): Acquia
ravi.shankar organization(s): OpenSense Labs
i-grou volunteering
Git commit message
Commit types
  • 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

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.