Use composite actions to setup scarb in this action
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, javascript
Research direction
Read the GitHub composite action documentation and inspect the current action structure in this repository. Compare its setup flow with software-mansion/setup-scarb, including how an optional argument could disable installation or how existing installations might be detected. Done means the action uses the reusable setup-scarb action while supporting users who manage Scarb themselves.
Written by the indexing model from the issue text.
Description
We can convert this action to be a composite action: https://docs.github.com/en/actions/creating-actions/creating-a-composite-action and setup scarb by reusing the https://github.com/software-mansion/setup-scarb action.
Details of this should be discussed but we need to remember to handle the cases where:
- User wants to configure scarb on their own - We should allow disabling installing scarb by an optional argument. Additionally we could do some automatic detection of scarb installation.
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from foundry-rs/setup-snfoundry
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
All issues in foundry-rs/setup-snfoundry
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sfbrigade/pocket-gardens#60 ·
Maintainers usually reply within 5 days
-
The print preview leaves writing space short by the margins of hidden headers, footers and solutionsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3329 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NativeScript/ios#577 ·
Maintainers usually reply within 1 day
-
could-have
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
01 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days