feat: configurable tests path, SHA releases, and psh shebang#3
Merged
hbahadorzadeh merged 7 commits intomainfrom Apr 28, 2026
Merged
Conversation
- Add tests_path input: path passed to pytest (directory, file, nodeids); defaults to project_path - Use INPUT_TESTS_PATH in step-test.sh instead of always running pytest on project root - Record sha-<short> in the JSONL release log for traceability (PyPI has no dist-tag equivalent) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replace the per-command psh check-and-wrap pattern with `#!/usr/bin/env psh` as the shebang so psh intercepts and logs every command in the script automatically. main.sh already invoked scripts directly so no change needed there. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…set -u Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Set Feather icon per action technology (anchor/activity/package/code/layers/cpu/shield for CI; upload-cloud/trending-up for CD) - Set marketplace color per action type - Add simple_icon field to pipery-action.toml (Simple Icons slug) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Code Review
This pull request updates the action to version 1.0.1, introducing a configurable tests_path for pytest, dynamic runner architecture detection, and enhanced marketplace branding. A significant architectural change is the transition of all step scripts to use the psh shebang, which is intended to automate command logging. Review feedback identifies a regression in src/step-build.sh where manual success logging was removed; this is inconsistent with other steps like lint and test and may break telemetry requirements defined in the configuration. Additionally, the CHANGELOG.md requires a formatting fix to merge duplicate 'Added' sections for the new version.
…s and restore build success logging
- Merge duplicate ### Added sections in CHANGELOG.md for 1.0.1
- Restore {"event":"build","status":"success"} log entry in step-build.sh
that was accidentally removed during psh shebang refactor; pipery-action.toml
requires a build event in the log file
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ts-path-and-sha-release
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tests_pathinput: configures the command or script run inside the container during the test stepsha-<7chars>) included in every release tag alongside semver#!/usr/bin/env pshas shebang for automatic JSONL loggingsetup-psh.shdetects runner architecture dynamically (amd64/arm64)config_fileloaded via dedicated step at action startsimple_iconfield topipery-action.tomlRelease
This PR cuts v1.0.1.
🤖 Generated with Claude Code