Contribution records
Draft
Contributors

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

Give credit to everyone
hooroomoo hooroomoo
nod_ nod_ volunteering organization(s): Très Bien Tech
xjm xjm volunteering organization(s): xjm
guptahemant guptahemant volunteering organization(s): QED42
shubh_ shubh511 organization(s): QED42
pradhumanjain2311 pradhumanjain2311 organization(s): OpenSense Labs customer(s): DrupalFit
utkarsh_33 Utkarsh_33 volunteering organization(s): Acquia
aadrian aadrian
grandmaglassesropeman grandmaglassesropeman volunteering
internetdevels InternetDevels.com
jelle_s jelles
kanav_7 kanav_7 organization(s): Google Summer of Code
rteijeiro rteijeiro organization(s): European Commission and European Union Institutions, Agencies and Bodies
smustgrave smustgrave organization(s): Mobomo
Sam Phillemon SamPhillemon volunteering organization(s): QED42
omkar-pd omkar-pd organization(s): QED42 customer(s): Drupal India Association
yash.rode yash.rode organization(s): Acquia
manuel garcia manuelgarcia volunteering
sahil.goyal sahil.goyal volunteering organization(s): Infoneo customer(s): Drupal India Association
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.