smartcontractkit / smartcontractkit/chainlink-cosmos
Gauntlet Inspection instruction ID
Open
Nobody has claimed this yet.
gauntlet
- Dominant language
- Go
- Stars
- 23
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Gauntlet inspections uses several query commands, that do not get tracked very well.
Original discussion: https://github.com/smartcontractkit/chainlink-terra/pull/39#discussion_r790625688
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 with the original discussion at pull request 39, then inspect the Gauntlet inspection query commands referenced in the issue. Clarify how instruction IDs should be assigned and tracked; done means the relevant query commands are consistently identifiable during inspections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100