Issue
Contribution records
Contributors

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

Give credit to everyone
atul_ghate volunteering organization(s): QED42
jrglasgow
Webbeh organization(s): Georgia Institute of Technology
ameymudras organization(s): Salsa Digital
nx2611 organization(s): Pantheon
prudloff organization(s): Insite
yashingole organization(s): QED42 customer(s): Drupal India Association
rfmarcelino
smustgrave organization(s): Mobomo
jcnventura organization(s): 1xINTERNET
danflanagan8 organization(s): Horizontal
daniel_j organization(s): WebFirst, Inc. customer(s): Yes& Agency
anybody volunteering organization(s): DROWL.de
sarikawirtz organization(s): 1xINTERNET
poker10 organization(s): ActivIT s.r.o.
grevil volunteering organization(s): DROWL.de
le72
asterovim volunteering
imyaro organization(s): Attico International
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
gaurav-mathur organization(s): Dotsquares Ltd.
j-vee volunteering
martijn de wit organization(s): Ablerz
nagy.balint organization(s): Webbtik.io
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.