Issue
Contribution records
Contributors

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

Give credit to everyone
lauriii organization(s): Druid
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
pfrenssen organization(s): Randstad Digital customer(s): European Commission and European Union Institutions, Agencies and Bodies
joelpittet organization(s): The University of British Columbia
faline organization(s): CI&T
benjifisher organization(s): Isovera
cilefen volunteering
vegantriathlete
mile23 volunteering
gigiabba organization(s): Ibuildings
MaskyS organization(s): Google Code-In
ankitjain28may volunteering organization(s): Google Summer of Code
mohit1604 organization(s): Google Summer of Code
andypost volunteering organization(s): Skilld
catch organization(s): Third and Grove
claudiu.cristea volunteering organization(s): Webikon
manuel garcia volunteering organization(s): Appnovation
john cook organization(s): Creode
ivan berezhnov volunteering organization(s): Drupal Ukraine Community customer(s): Levi9
Maheshwaran.j volunteering organization(s): DrupalPartners customer(s): Binary Works
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.