NucleoidMC / NucleoidMC/server-wrapper
Allow specifying what Actions run to check
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 6
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 1
Description
In a monolithic repo, a person could use different action workflows to build different mods only when they're updated.
Being able to specify which workflow to check would be extremely helpful for such a setup!
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
No files, tests, or entry points are named. Start by locating the existing logic that checks GitHub Actions workflows and how mod updates select artifacts; then define how a mod specifies its workflow and verify that only the selected workflow is checked for that mod.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100