Status page // Unofficial fan work
A live status page for the undecuple GitHub projects.
It shows what each project is doing: build state, last push, releases and open items.
Open the site · Project docs · How it works · Setup · Profile
- A table of every public repository of the account: CI state, last push, latest release, stars, forks, open pull requests and issues. Sort it by activity, name, stars, forks, CI, pull requests or release.
- Contributions: the pull requests and issues the account has opened in other people's repositories, 10 per page, newest first.
- Recent activity: a feed of public events, newest first.
- Project docs: pages that explain the projects, with playable step-by-step diagrams. Today: how a re:psn server introduces players, and how a PS3 game becomes a native PC program with ps3recomp.
- Comments through giscus (GitHub Discussions in this repository).
The look is ANSI/NFO: a block-letter banner, double-line frames and 16 colours. The colours follow guts.nvim.
tools/status.pyreads the GitHub API (GET only, public repositories) and writesstatus.json..github/workflows/pages.ymlis the only automation. It buildsstatus.json, copies the site files into the Pages artifact and deploys it. It runs on every push tomain, by hand, and on a schedule of every 10 minutes. GitHub often delays or skips scheduled runs, so the page says when its data was generated.- When the page loads it also asks the GitHub API for stars, forks, last push and recent activity, so those stay current even when a scheduled run was skipped. CI, pull requests, releases and contributions are as of the generated time.
app.jsdraws the page in the browser. All text goes throughtextContent. Links go only tohttps://github.com/, plus the fixed Ko-fi support link and the Discord invite (a link only; nothing is loaded from Discord). The page contactsapi.github.com(the live numbers) and, only when comments are enabled,giscus.app. It sets no cookies and loads no external fonts.- The project docs pages use
play.js, which plays the scenarios inre-psn.jsonandps3recomp.json. - The workflow needs
contents,actions,discussions(read),pagesandid-tokenpermissions on the built-in token. It pins its actions by commit. - Comments use giscus: one discussion for the whole site, titled "Site Discussions", in the category Announcements, so only the giscus bot opens threads.
status.pyreads the repository id and the category id with one GraphQL read query and puts them instatus.json.
- Settings, Pages: set Source to GitHub Actions.
- Run the
pagesworkflow once (Actions, Run workflow). - For comments: turn Discussions on and install the giscus app for the repository.
- For the social preview: Settings, General, Social preview, upload
assets/social-preview.png(1280x640).
GitHub turns off scheduled workflows in a public repository after 60 days without activity. Each scheduled run enables the workflow again through the API and, once a day, commits status.json to a snapshot branch. Whether either resets the 60-day timer is not confirmed by GitHub. If the page shows "status.json is N h old", re-enable the workflow under Actions or push to main.
Private repositories are never listed. The script skips them and uses a token that cannot read them.
The site also hosts the contact forms for the ps3rc-feed project. Open an issue to correct a wrong label, ask for a listing to be removed, or report a bug on the page or feed. Do not put passwords, tokens, game files or private information in an issue.
Do not report a security problem in a public issue. Write to undecuple@proton.me.
This site was developed with AI agent assistance under the maintainer's direction. A person reads and approves the text before it is posted.
MIT, see LICENSE.