slimtoolkit / slimtoolkit/slim
Read Config from YML File
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
In some cases, I get these really long unwieldy build strings that are difficult to manage. Also, in many cases, there are parameters that are repeated across different builds (e.g. including git or jq). I was thinking it would be great if we could store our build config for each build in a YML file. Are there already plans to support this? If not, I was thinking about writing a supplementary NPM package that would handle this for us.
Just looking for any ideas/recommendations before I write something that no one ends up using.
Contributor 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.
Research direction
The issue does not identify any files, tests, or entry points. First clarify whether YAML build configuration belongs in the project and whether an NPM package is desired, then define the supported configuration shape and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100