aRustyDev / aRustyDev/tmpl-rust
Actions
- Dominant language
- Just
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- check for new action vers
- create issue if new vers exist
- update env.vars if new vers exist
On schedule
- run check new ver workflow
- if actions are successful update var.gate for main workflow (ie don't run it; since it ran successfully) & update var.stable_ver for each action.
> not sure how to use Environments here, but they should be added later.
Cache should be managed for toolchain setups
Try to cache builds too. But lower priority than toolchains.
Figure out what attestations need to look like; SBOM vs bin vs src vs tests vs perf/bench vs fuzz.
Figure out how to gate build targets based on project configs. (Ie container vs local binary... etc)
Figure out how to structure releases based to accommodate containers, binaries, licenses, READMEs, docs etc
Figure out how to gate binary vs libs
Figure out how to serve both rust docs and MDBook for src docs and app level logic
Contributor guide
Assessment
This issue has not been assessed yet.