Issue
Contribution records
Contributors

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

Give credit to everyone
cilefen
andypost volunteering organization(s): Skilld
TBI
dinesh18 volunteering
svdhout organization(s): Calibrate
borisson_ volunteering
gngn organization(s): Computer Manufaktur GmbH
blacksnipe
nuez
enrocean167 organization(s): Aubergine IT
philkay
vdsh volunteering
semiaddict
madhu_h organization(s): Acquia customer(s): Acquia
anybody organization(s): DROWL.de
vistree
quietone organization(s): PreviousNext
akashkumar07 organization(s): TO THE NEW
catch organization(s): Third and Grove
reenaraghavan
mohit_aghera volunteering organization(s): PreviousNext
smustgrave organization(s): Mobomo
lauriii organization(s): Acquia
drupalfan2 volunteering
dunebl
kala4ek volunteering
arnalyse
sboden volunteering
Patrick Bauer
aarti zikre volunteering organization(s): QED42
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.