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

Not getting logged in when setting GITHUB_TOKEN env

Open
#7,197 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
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github

Research direction

Start by reproducing the reported startup command with GITHUB_TOKEN set, then inspect the attached main-logs.txt for authentication-related failures. Compare the expected GitHub Actions and Pull Requests login behavior with the actual sign-in prompt; done means the token is recognized without an interactive sign-in.

Written by the indexing model from the issue text.

Description

bug triage
Is there an existing issue for this?
  • I have searched the existing issues
OS/Web Information
  • Web Browser: Chrome 133
  • Local OS: win11
  • Remote OS: ubuntu 24.04
  • Remote Architecture: amd64
  • code-server --version: 1.96.4
Steps to Reproduce
  1. Create workspace
  2. mounted home directory
  3. run the following in startup_script
  4. export GITHUB_TOKEN=<>
  5. /app/code-server/bin/code-server --auth none --port 13337
Expected

Be logged into Github Actions, Pull Requests, etc

Actual

Getting asked to sign in with Github to use *

main-logs.txt

Logs
look above it was too big
Screenshot/Video

Image

Does this bug reproduce in native VS Code?

This cannot be tested in native VS Code

Does this bug reproduce in GitHub Codespaces?

This cannot be tested in GitHub Codespaces

Are you accessing code-server over a secure context?
  • I am using a secure context.
Notes

No response

Dominant language
TypeScript
Stars
79.4k
Forks
6.9k
Avg merge
2d 13h
Merged PRs (30d)
39

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 coder/code-server

All issues in coder/code-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.