Add commit tests

[crazywhalecc]

What does this PR do?

Checklist before merging

If your PR involves the changes mentioned below and completed the action, please tick the corresponding option.
If a modification is not involved, please skip it directly.

• If you modified *.php, run composer cs-fix at local machine.
• If it's an extension or dependency update, make sure adding related extensions in src/global/test-extensions.php.
• If you changed the behavior of static-php-cli, update docs in ./docs/.
• If you updated config/xxx.json content, run bin/spc dev:sort-config xxx.

[Copilot]

Pull Request Overview

This PR introduces default handling for shared extensions, updates documentation to reflect the new option, and adds a GitHub Actions workflow to parse commit message tags and run craft/bash tests automatically.

• Provide an empty-array default for shared-extensions in CraftCommand
• Document the shared-extensions key under build-options
• Add .github/workflows/commit-tests.yml to conditionally run tests based on {craft} and {bash} tags

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/SPC/command/CraftCommand.php	Default missing shared-extensions to an empty array
docs/deps-craft-yml.md	Add shared-extensions: [] sample under build-options
.github/workflows/commit-tests.yml	New workflow to parse commit tags and run craft/bash tests

Comments suppressed due to low confidence (6)

src/SPC/command/CraftCommand.php:52

• Add or update unit/integration tests to cover the scenario when shared-extensions is not provided, ensuring that the default empty array case behaves as expected.

$shared_extensions = implode(',', $craft['shared-extensions'] ?? []);

docs/deps-craft-yml.md:45

• Indent this comment line and the following key so they correctly appear under the build-options block with the same two-space indentation as the other YAML entries.

# Build options for shared extensions (same as `build-shared` command options, all options are optional)

.github/workflows/commit-tests.yml:35

• This exit 0 halts the entire parsing script when {craft} tags are missing, preventing downstream parsing of Bash tags or prefix/OS settings. Consider removing or replacing it to allow the script to continue processing.

            exit 0

.github/workflows/commit-tests.yml:36

• Explicitly set skip_craft=no when craft tags are found to make the workflow logic clearer and avoid relying on an empty default.

          else

.github/workflows/commit-tests.yml:51

• In the Bash parsing block, explicitly set skip_bash=no when {bash} tags are found to make the condition more transparent.

          else

.github/workflows/commit-tests.yml:1

• [nitpick] The workflow name is Single Test but it runs both craft and bash jobs. Consider renaming it to something like Commit Tests to better reflect its purpose.

name: Single Test

[henderkes]

I'm on a short weekend trip, I can leave a proper review tomorrow evening

[crazywhalecc]

I'm on a short weekend trip, I can leave a proper review tomorrow evening

Ah no problem. I'll leave tomorrow, too. Enjoy your weekend!

[crazywhalecc]

Looks good to me now. I also updated the PR template.