shanselman / shanselman/github-artifacts-analyzer
Error: injected env (0) from .env
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 118
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I have installed github-artifacts-analyzer globally using the following command:
npm install -g github-artifacts-analyzer
I have created a token in github with the necessary permissions to access all repos.
Using Github bash on Windows, I login to github cli using the following command:
gh auth login
Running the following command:
github-artifacts analyze
produces the following error:
injected env (0) from .env
I have also tried with the following methods:
github-artifacts analyze -token TOKENSTRING
Using an windows environment variable named: GITHUB_TOKEN
Using an .env file with the following contents in the file
GITHUB_TOKEN=TOKENSTRING
Every method tried results with the error:
injected env (0) from .env
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
Reproduce the issue with github-artifacts analyze after trying the documented -token TOKENSTRING, GITHUB_TOKEN, and .env approaches. Trace the CLI entry point and environment-loading path to determine why it reports injected env (0) from .env; done means authentication works and the analyze command starts without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100