Contribution records
Contributors

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

Give credit to everyone
joachim joachim volunteering
bhumikavarshney BhumikaVarshney volunteering organization(s): QED42
saschaeggi saschaeggi volunteering organization(s): GitLab
meeni_dhobale meeni_dhobale volunteering organization(s): QED42
smustgrave smustgrave organization(s): Mobomo
nod_ nod_ organization(s): Très Bien Tech customer(s): OPTASY, Palantir.net, Vardot
sakthi_dev sakthi_dev organization(s): Specbee customer(s): Drupal India Association
zaryab_drupal zaryab_drupal
xjm xjm organization(s): HeroDevs, xjm
gauravvvv Gauravmahlawat organization(s): Axelerant customer(s): Drupal India Association
ahsannazir ehsann_95 organization(s): QED42
shweta__sharma shwetaoti organization(s): OpenSense Labs
kanchan bhogade Kanchan-Bhogade organization(s): QED42 customer(s): Drupal India Association
rifas-ali-pbi rifas-ali-pbi organization(s): Valuebound customer(s): Valuebound
shashwat-tiwari shashwat-tiwari organization(s): Specbee customer(s): Drupal India Association
mithun s Mithun_S customer(s): QED42
anicoto anicoto organization(s): Cellar Door
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.