Skip to content

Add packages input parameter#22

Merged
Sewer56 merged 1 commit intov1-masterfrom
add-packages-input
Feb 14, 2026
Merged

Add packages input parameter#22
Sewer56 merged 1 commit intov1-masterfrom
add-packages-input

Conversation

@Sewer56
Copy link
Copy Markdown
Member

@Sewer56 Sewer56 commented Feb 14, 2026

Summary

Adds support for the new packages input parameter introduced in devops-rust-test-and-coverage.

Changes

  • Added packages input parameter to action.yml
  • Passed packages through to the devops-rust-test-and-coverage action
  • Documented the parameter in README.MD
  • Added clarifying note that the parameter does not affect build output

Usage

- uses: Reloaded-Project/devops-rust-lightweight-binary@v1
  with:
    target: x86_64-unknown-linux-gnu
    run-tests-and-coverage: true
    packages: |
      package-a
      package-b

Benefits

  • Users can now selectively test specific packages in multi-package workspaces
  • Consistent with upstream devops-rust-test-and-coverage action API
  • Clear documentation prevents confusion about build vs test scope

…rage

Adds support for the new `packages` input parameter introduced in
devops-rust-test-and-coverage v1. This allows users to specify which
packages to test instead of testing the entire workspace.

Changes:
- Added `packages` input parameter to action.yml
- Passed `packages` to the test-and-coverage action
- Documented the parameter in README.MD
- Added note clarifying the parameter does not affect build output

Benefits:
- Users can now selectively test specific packages in multi-package workspaces
- Consistent with upstream devops-rust-test-and-coverage action API
- Clear documentation prevents confusion about build vs test scope
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 14, 2026

Walkthrough

The changes add a new packages input parameter to the action. This parameter accepts a multi-line list of packages per line and is passed through to the devops-rust-test-and-coverage action. When empty, all workspace packages are tested. The parameter is documented in both the README and action.yml configuration files, and does not affect which binary is built.

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: adding a new packages input parameter to the action.
Description check ✅ Passed The description clearly relates to the changeset, explaining the purpose of adding the packages parameter, documenting the changes across files, and providing usage examples.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into v1-master

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch add-packages-input

No actionable comments were generated in the recent review. 🎉


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@Sewer56 Sewer56 merged commit ecf42e4 into v1-master Feb 14, 2026
2 checks passed
@Sewer56 Sewer56 deleted the add-packages-input branch February 14, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant