Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

adding/changing a Repository Secret that requires Auth, causes it to fail silently

Open
#513 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, typescript, vscode

Research direction

Start by reproducing the failure in Cursor or VS Code using extension version v0.27.2, while adding or editing API_SERVER_SSH_KEY or another repository secret requiring authentication. Investigate how the extension handles the operation and determine whether authentication can be provided; otherwise, done means showing a clear error or login/authentication indication instead of failing silently.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
When adding a secret that requires authentication in Github, it fails silently due to no auth functionality in the extension

To Reproduce
Steps to reproduce the behavior: try adding a API_SERVER_SSH_KEY or something that requires authentication

  1. With this workflow: 'access the extension from cursor or vscode'
  2. Do this: 'create a new secret key or edit an existing one'
  3. See error : there is no error it just fails silently.

Expected behavior
Ideally it should provide a way to authenticate. If there is no way to authenticate in cursor or vscode, there should at least be some error or indication that you need to login to github and/or authenticate.

Screenshots
If applicable, add screenshots to help explain your problem.

Extension Version
v0.27.2

Additional context
I am running cursor

Dominant language
TypeScript
Stars
661
Forks
214
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/vscode-github-actions

All issues in github/vscode-github-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.