Issue
Contribution records
Contributors

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

Give credit to everyone
berdir organization(s): MD Systems GmbH
kfritsche
penyaskito volunteering organization(s): Cocomore AG
xano
mgifford organization(s): OpenConcept Consulting Inc.
andypost volunteering organization(s): Skilld
Mirroar organization(s): werk21
alexej_d
merilainen organization(s): Mearra (formerly known as Wunder)
mpp organization(s): AmeXio Fuse customer(s): District09
borisson_ volunteering
catch organization(s): Third and Grove
larowlan organization(s): PreviousNext
anybody organization(s): DROWL.de
pcambra organization(s): Cambrico
bbrala volunteering organization(s): SWIS
smustgrave organization(s): Mobomo
godotislate volunteering
kristiaanvandeneynde organization(s): Factorial.io
brockfanning
wim leers organization(s): Acquia
gábor hojtsy organization(s): Acquia
alan d.
claudiu.cristea volunteering organization(s): Webikon
samitk organization(s): Material customer(s): Drupal India Association
nicxvan organization(s): nLightened Development LLC
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.