Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
andypost volunteering organization(s): Skilld
larowlan volunteering
mirom organization(s): i-KOS
rteijeiro organization(s): Tieto
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios) customer(s): Drupal Association
zserno
joelpittet
Bojhan
webchick organization(s): Acquia
tkoleary organization(s): Acquia
balintcsaba volunteering
mortona2k
anas_maw volunteering
ankithashetty volunteering organization(s): Specbee
vakulrai volunteering organization(s): QED42 customer(s): QED42
yogeshmpawar organization(s): Portage CyberTech
dqd volunteering organization(s): MAROQQO studios
joachim volunteering
catch organization(s): Third and Grove
rkoller
mherchel
aaronmchale volunteering
cedewey organization(s): DevCollaborative, LLC
jacobupal
gábor hojtsy organization(s): Acquia
david.lukac volunteering
wim leers organization(s): Acquia
greg.b volunteering
nick hope
ravi.shankar organization(s): OpenSense Labs
ramya balasubramanian organization(s): Material
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.