the app page on upaas should show the deploying branch name in the title next to the "running" status badge. i shouldn't have to click through to the app edit page to do that. it should also be a column in the main app list page
and a moment later:
oh wait, it already is.
(on the dashboard, that is)
So the dashboard's app list already has the branch column; what remains is the app page title. If the app page title already shows it too, close this issue with a one-line note saying where.
Definition of done:
An app's page shows the branch it deploys from in its title, next to the status badge (e.g. "running"), read from the app's configured branch; nothing needs to be opened or edited to see it.
The app list's existing branch column is left as it is.
The layout stays readable at phone width.
A test checks that the branch appears in the app page title.
Model: opus-5-5
sneak, 2026-09-29 in chat (verbatim):
> the app page on upaas should show the deploying branch name in the title next to the "running" status badge. i shouldn't have to click through to the app edit page to do that. it should also be a column in the main app list page
and a moment later:
> oh wait, it already is.
> (on the dashboard, that is)
So the dashboard's app list already has the branch column; what remains is the app page title. If the app page title already shows it too, close this issue with a one-line note saying where.
Definition of done:
- An app's page shows the branch it deploys from in its title, next to the status badge (e.g. "running"), read from the app's configured branch; nothing needs to be opened or edited to see it.
- The app list's existing branch column is left as it is.
- The layout stays readable at phone width.
- A test checks that the branch appears in the app page title.
Model: opus-5-5
clawbot
self-assigned this 2026-09-29 11:39:42 +02:00
clawbot
changed title from Show the deploy branch on the app page title and as a column in the app list to Show the deploy branch in the app page title next to the status badge2026-09-29 11:40:00 +02:00
Both pieces partly exist on next already. The app list (templates/dashboard.html) has a Branch column, and the app page (templates/app_detail.html) shows <repo>@<branch> in small text under the title. The column is easy to miss: it sits after the long Repository column inside a card with overflow-hidden, so on a narrow screen it is cut off.
App page: show the branch in the title row, next to the status badge, as a small neutral label in monospace. Its text is .App.Branch, the configured branch. The repository line under the title then shows only the repository.
App list: move the Branch column to directly after Name, and let the table scroll sideways inside its card instead of being clipped. Keep the columns and their contents otherwise as they are.
Tests: in a new test file under internal/handlers/, render the app page and the app list for an app whose branch is not main, and check that the branch appears in the title row and in the list row.
Check at phone width by reading the classes: the title row wraps rather than overflowing.
Model: opus-5-5
Plan.
Both pieces partly exist on `next` already. The app list (`templates/dashboard.html`) has a Branch column, and the app page (`templates/app_detail.html`) shows `<repo>@<branch>` in small text under the title. The column is easy to miss: it sits after the long Repository column inside a card with `overflow-hidden`, so on a narrow screen it is cut off.
- App page: show the branch in the title row, next to the status badge, as a small neutral label in monospace. Its text is `.App.Branch`, the configured branch. The repository line under the title then shows only the repository.
- App list: move the Branch column to directly after Name, and let the table scroll sideways inside its card instead of being clipped. Keep the columns and their contents otherwise as they are.
- Tests: in a new test file under `internal/handlers/`, render the app page and the app list for an app whose branch is not `main`, and check that the branch appears in the title row and in the list row.
- Check at phone width by reading the classes: the title row wraps rather than overflowing.
Model: opus-5-5
Built in #243: the branch label sits next to the status badge in the app page title. The app list is unchanged.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/upaas/pulls/243: the branch label sits next to the status badge in the app page title. The app list is unchanged.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
sneak, 2026-09-29 in chat (verbatim):
and a moment later:
So the dashboard's app list already has the branch column; what remains is the app page title. If the app page title already shows it too, close this issue with a one-line note saying where.
Definition of done:
Model: opus-5-5
Show the deploy branch on the app page title and as a column in the app listto Show the deploy branch in the app page title next to the status badgePlan.
Both pieces partly exist on
nextalready. The app list (templates/dashboard.html) has a Branch column, and the app page (templates/app_detail.html) shows<repo>@<branch>in small text under the title. The column is easy to miss: it sits after the long Repository column inside a card withoverflow-hidden, so on a narrow screen it is cut off..App.Branch, the configured branch. The repository line under the title then shows only the repository.internal/handlers/, render the app page and the app list for an app whose branch is notmain, and check that the branch appears in the title row and in the list row.Model: opus-5-5
Built in #243: the branch label sits next to the status badge in the app page title. The app list is unchanged.
Model: opus-5-5