-
Notifications
You must be signed in to change notification settings - Fork 854
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Which interface did you use?
CLI
Repository URL (if public)
No response
Git host
Other (specify below)
Other Git host
Local repo
Repository visibility
private
Commit, branch, or tag
default branch
Did you ingest the full repository or a subdirectory?
full repository
Operating system
macOS
Browser (Web UI only)
Not relevant (CLI / PyPI)
Other browser
No response
Gitingest version
v0.3.0
Python version
No response
Bug description
GitIngest is now broken for local repos for me. It is validating my "GitHub" token, and saying it is invalid — but I am not even using GitHub. Here's the console output.
❯ uv tool run gitingest .
Analyzing source, output will be written to 'digest.txt'...
Error: Invalid GitHub token format. To generate a token, go to https://github.com/settings/tokens/new?description=gitingest&scopes=repo.
2025-07-31 09:49:43.577 | INFO | gitingest.entrypoint:ingest_async:89 | Starting ingestion process | {"source":"."}
Aborted!
I'd suggest not validating any GitHub tokens, etc. when a local repo is being ingested.
Steps to reproduce
Expected behavior
Gitingest working as normal and creating digest.txt
, like it did in previous releases.
Actual behavior
Gitingest fails, due to trying to validate a GitHub token that isn't needed.
Additional context, logs, or screenshots
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working