Problem
When a GitHub repository URL is pasted, the workspace only shows minimal info:
- Generic "GitHub repository" badge
- Repo name
- Hardcoded description: "GitHub repository ready for import and training setup."
- Empty Model Details card
This is in stark contrast to HF model links which fetch rich structured data (architecture, parameters, pipeline, license, tags, README, benchmark results).
Expected Behaviour
GitHub repos should fetch and display structured metadata from the GitHub API, including:
- Description — repo description from GitHub API
- Stats — stars, forks, open issues, watchers
- Language — primary programming language
- Topics/Tags — repo topics as tag pills
- License — license type
- Last updated / Created — timestamps
- README — rendered markdown from
README.md
- Model Details — auto-detect if it's an ML repo (presence of
requirements.txt, model files, config files like config.json, tokenizer.json) and surface relevant fields
Current Behaviour
All GitHub repos show the same hardcoded placeholder data regardless of what the repo actually contains.
Root Cause
_fetch_github_preview() in app/state/app_state.py makes a GitHub API call but does not populate the structured preview fields (preview_architecture, preview_params, preview_tags, preview_readme, etc.) that the workspace UI expects.
Steps to Reproduce
- Paste any GitHub URL (e.g.
https://github.com/ggerganov/llama.cpp)
- Confirm the preview
- Observe the workspace shows empty Model Details and no README/tags
Suggested Fix
Extend _fetch_github_preview() to:
- Call
GET /repos/{owner}/{repo} for description, stars, forks, language, license, topics
- Call
GET /repos/{owner}/{repo}/readme for README content
- Map the response fields to the same
preview_* state vars used by HF previews
Environment
- TuneOS
app/state/app_state.py — _fetch_github_preview method
- Reflex frontend workspace view —
app/pages/landing.py
Problem
When a GitHub repository URL is pasted, the workspace only shows minimal info:
This is in stark contrast to HF model links which fetch rich structured data (architecture, parameters, pipeline, license, tags, README, benchmark results).
Expected Behaviour
GitHub repos should fetch and display structured metadata from the GitHub API, including:
README.mdrequirements.txt, model files, config files likeconfig.json,tokenizer.json) and surface relevant fieldsCurrent Behaviour
All GitHub repos show the same hardcoded placeholder data regardless of what the repo actually contains.
Root Cause
_fetch_github_preview()inapp/state/app_state.pymakes a GitHub API call but does not populate the structured preview fields (preview_architecture,preview_params,preview_tags,preview_readme, etc.) that the workspace UI expects.Steps to Reproduce
https://github.com/ggerganov/llama.cpp)Suggested Fix
Extend
_fetch_github_preview()to:GET /repos/{owner}/{repo}for description, stars, forks, language, license, topicsGET /repos/{owner}/{repo}/readmefor README contentpreview_*state vars used by HF previewsEnvironment
app/state/app_state.py—_fetch_github_previewmethodapp/pages/landing.py