canonical / canonical/source-wand
[Issue] With Go, how do we deal with version name when it's the commit hash?
Open
Nobody has claimed this yet.
go
protocol
- Dominant language
- Rust
- Stars
- 9
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Why is this important?
- Creating the
source-wand.yamlis all automated >>versionandsourcecraft_tracknames need to be generated correctly
What we are waiting for?
- Protocol on naming conventions
What happens when we get protocol
- Follow the protocol for version naming when we generate the
source-wand.yaml>> logic to handle version naming when it is a commit
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
Start by locating the automation that generates source-wand.yaml and the version and sourcecraft_track fields. Resolve the naming protocol for Go versions represented by commit hashes, then update generation logic and verify that generated YAML follows the agreed convention.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100