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

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

Open
#474 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

Description

enhancement

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"

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"

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

Dominant language
TypeScript
Stars
661
Forks
214
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.