Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
irinaz volunteering organization(s): Fibonacci Web Studio
damienmckenna organization(s): Current
drumm organization(s): Drupal Association
bhanu951 volunteering
saschaeggi organization(s): GitLab
hestenet organization(s): Drupal Association
alexpott organization(s): Acro Commerce, Thunder
spleshka organization(s): SystemSeed customer(s): SystemSeed
lauriii organization(s): Acquia
xurizaemon organization(s): Catalyst IT
jonnyeom volunteering
grimreaper organization(s): Smile
lussoluca organization(s): SparkFabrik
phenaproxima organization(s): Acquia
kingdutch volunteering
christianadamski
bradjones1 organization(s): Not Vanilla, Inc.
jungle volunteering
cmlara
zaporylie organization(s): Ny Media AS
jonathan1055 volunteering
markdorison organization(s): Chromatic
dww volunteering
ayalon organization(s): Liip
mkalkbrenner organization(s): Jarltech Europe GmbH customer(s): SearchStax
feyp volunteering organization(s): werk21
naveenvalecha organization(s): Morpht customer(s): Morpht
tanc volunteering
hongpong volunteering organization(s): Feidt Design
chr.fritsch organization(s): Thunder
wim leers organization(s): Acquia
finn lewis volunteering organization(s): Agile Collective
moshe weitzman organization(s): Commonwealth of Massachusetts
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.