Contribution records
Draft
Contributors

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

Give credit to everyone
damiankloip damiankloip
xjm xjm
ekes ekes
oadaeh oadaeh
killua99 killua99
dawehner dereine customer(s): Drupal Association
amitgoyal amitgoyal
larowlan larowlan
pcambra pcambra
fgm fgm organization(s): OSInet
andypost andypost volunteering organization(s): Skilld
gaydabura gaydabura volunteering organization(s): Skilld
pk188 pk188 organization(s): OpenSense Labs
vsujeetkumar vsujeetkumar organization(s): Material customer(s): Drupal India Association
hardik_patel_12 Hardik_Patel_12 organization(s): QED42 customer(s): Drupal India Association
smustgrave smustgrave organization(s): Mobomo
quietone quietone organization(s): PreviousNext
manuel garcia manuelgarcia volunteering
batigolix batigolix volunteering organization(s): Finalist
bserem bserem organization(s): Annertech
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.