overdrivenpotato / overdrivenpotato/rust-psp
CI features not carried over after workspace migration
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 826
- Forks
- 44
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
I think we should make a feature in the ci crate that propogates to the feature in the psp crate for this
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the workspace manifests and the feature declarations in the ci and psp crates. Trace how the relevant feature is defined and enabled during CI, then verify the migration path with the repository's existing checks. Done means the CI crate's feature is carried over to the corresponding psp feature without breaking workspace builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100