Add Go toolset to PATH in our internal pipelines to allow Component Governance to use it
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
CG wants to use go to examine go.mod files for dependencies.
We could either add the Go we build or the bootstrap Go to PATH to satisfy CG.
I think we should only add it to PATH near the end of our build, to continue making sure it is not in PATH during "our" part of the pipeline (in case it is accidentally used, which should result in a failure).
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 internal pipeline configuration and identify the step that runs Component Governance, then review how the build and bootstrap Go are exposed. The change is complete when Component Governance can inspect go.mod files while Go remains absent from PATH during the project's own build steps; no specific file or test is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100