GoogleCloudPlatform / GoogleCloudPlatform/scion
Flexible Context System
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.7k
- Forks
- 266
- Avg merge
- 7h 6m
- Merged PRs (30d)
- 447
Description
## Problem / Motivation
I was checking out KubeOpenCode (still like Scion better, but there are some useful ideas)
https://kubeopencode.github.io/kubeopencode/docs/features/context-system
## Proposed Solution
A way to specify extra context (repos, harness inputs) in configuration, that are merged like other harness pieces.
## Alternatives Considered
A pre-run hook?
## Additional Context
this is what I'm after, in a configurable way ;]
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
Read the linked KubeOpenCode context-system documentation first, then locate Scion’s configuration handling and harness assembly paths. Clarify how extra repositories and harness inputs should be configured and merged, and define done as a documented, configurable context mechanism with behavior consistent with existing harness pieces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100