actions / actions/starter-workflows
In reference to https://github.com/cli/cli/issues/1735
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
In reference to https://github.com/cli/cli/issues/1735
Many organizations use TLS Inspection for security purposes on internet traffic. Currently there is no way in gh or other commands relying on go-gh. As per this comment from @babakks - https://github.com/cli/cli/issues/1735#issuecomment-3167529911 - any solution with env vars would need to happen in go-gh rather than gh cli
I noticed that no issue had been created here and there was no additional follow up on the issue in the cli repo. Hoping to get this pushed forward, as some organizations will be unwilling to allow bypassing inspection at the firewall.
Originally posted by @mnooseman in https://github.com/cli/go-gh/issues/212
Contributor guide
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 reviewing cli/cli issue 1735 and the referenced comment, then confirm whether go-gh is the appropriate entry point rather than gh. Define what TLS Inspection support should cover and how completion would be verified; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100