Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
xano organization(s): Druid
berdir organization(s): MD Systems GmbH
fabianx volunteering
jibran volunteering
joachim
psf_ organization(s): SDOS
jungle volunteering
swatichouhan012 organization(s): Valuebound customer(s): Valuebound
hardik_patel_12 organization(s): QED42
jofitz organization(s): jofitz
deepakaryan1988 volunteering organization(s): Trigyn Technologies Ltd
jpatel657 organization(s): Trigyn Technologies Ltd
martin107 volunteering
quietone volunteering
hash6 organization(s): QED42 customer(s): Drupal India Association
vsujeetkumar organization(s): Material customer(s): Drupal India Association
mohit_aghera organization(s): QED42
tim.plunkett organization(s): Acquia
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
wim leers organization(s): Acquia
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.