No command palette option to sign in, and also no way to know that errors are occurring because you're not signed in.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- authentication, developer-experience
Research direction
Start by tracing the command palette flow for “github actions” and the validation errors shown for env access. Done means users can discover a sign-in action from the relevant command palette context and unauthenticated errors clearly explain that signing in is required.
Written by the indexing model from the issue text.
Description
Describe the bug
I had no idea I was able to sign in. Been dealing with this nonsense for over a year: #222
To Reproduce
- Press Ctrl+Shift+P to open command palette
- Type "github actions"
- Observe that there is no sign in option.
There is an option called "focus on view" which does then give you a sign in option.
Expected behavior
An option to sign in.
Screenshots
You can imagine.
Extension Version
v0.27.0
Additional context
Probably what happened (months ago)
- I open a yaml file.
- vscode tells me to install a recommended extension.
- it prompts me to log in so I can access my workflows.
- Of course I'm going to dismiss it immediately because I already have my yml file open and it's a popup. If it said "you will get spurious errors all over your yaml file" then I may have thought twice.
I feel like the error info on the "env" access should say "you need to be logged in" or something.
- Dominant language
- TypeScript
- Stars
- 661
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
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.
More from github/vscode-github-actions
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/vscode-github-actions#627 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
github/vscode-github-actions#630 · 1 reaction ·
-
long work Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
github/vscode-github-actions#628 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
github/vscode-github-actions#625 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 64/100
github/vscode-github-actions#621 · 3 comments ·
All issues in github/vscode-github-actions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 88/100