Version hashes: in Project and Lightning, use the v2 spec format (not state format)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Version hashes currently use the provisioner state structure to generate a hash from. This ensures that keys are the same across both repos when compiling the version hash.
Since updating the portability spec and standardising on the v2 spec format, we should be using this representation in both repos as the primary representation of a workflow.
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
Locate the version-hash generation and workflow representation code in the Project and Lightning repositories. Compare the current provisioner state-based input with the v2 portability spec format; done means both repositories use the v2 workflow representation as the primary input for version hashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100