liquidmetal-dev / liquidmetal-dev/flintlock
Use a different token for the e2es
Open
Nobody has claimed this yet.
kind/test
lifecycle/stale
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
This should be a bot token but i think right now it is one of mine
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
The issue names only the e2es and the token, not a file or test. Locate the end-to-end test configuration and identify where the current token is sourced; done means the e2es use a bot token without exposing credentials and the relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100