github / github/vscode-github-actions

make sign-out / sign-in possible with multiple accounts

Open
#474 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
660
Forks
213
PR merge metrics
No merged PRs in 30d

Description

Many developers have multiple Git-Accounts:

- work
- university
- private accounts
- public (and non-work, non-university related) accounts

(For simplicity let us just make the unrealistic assumption that all of these git accounts are on GitHub.)

The GitHub Pull Request extension in MS VSCode respects these. (I guess it just observes what the local .git/config is.)

![Command Palette for "GitHub Pull Request"](https://github.com/user-attachments/assets/9b06083b-f774-4f64-bd0d-3f8a598d6faf)

But the GitHub Actions extension in VSCode does not.
There is not even the option to "sign in/out" and manually select an account. (I think you do it once and cannot change it thereafter.)

![Command Palette for "GitHub Actions"](https://github.com/user-attachments/assets/e0203e55-8a66-4c65-bf3b-e2fdca591537)

## Proposed solution ##

I would like to see e.g.

1. a Command Palette menu option to sign in/out for the GitHub Actions extension


or the Actions and PR extensions should have synchronised settings
(vis-a-vis current account for current workspace)

2. the ability to possible set Git[Hub] Account at the (VSCode) profile level

3. possibly a way to do select accounts via VSCode's (local or global) **settings.json**

Contributor guide

Open the contributing guide

Research direction

Start by comparing the GitHub Actions and GitHub Pull Request extension sign-in behavior, including the local .git/config and VS Code Command Palette. Review how VS Code profiles and local or global settings.json could represent an account, then define a consistent sign-in/sign-out flow with workspace-level account selection as the completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, github-actions, typescript, vscode
Domain
authentication, developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.