Skip to content

Stack template row actions under the title on mobile - #255

Merged
steezeburger merged 1 commit into
mainfrom
ccr-10782aa9-uizgmo
Oct 2, 2026
Merged

Stack template row actions under the title on mobile#255
steezeburger merged 1 commit into
mainfrom
ccr-10782aa9-uizgmo

Conversation

@steezeburger

@steezeburger steezeburger commented Oct 1, 2026

Copy link
Copy Markdown
Owner

On phones the templates page squeezed each template name into a narrow column beside the Use / Add to page… / Edit buttons. Below 768px the actions now sit on their own row under the name and modified date. The row's action buttons also use theme colors now, so the Edit link no longer shows up link-blue. CSS only; desktop layout is unchanged.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CYa1RCQHxScbnkMG3UJZvR

Generated by Claude Code

@claude
Stack template row actions under the title on mobile
65d2534 
Below 768px the templates list squeezed the name into a narrow column
beside the Use / Add to page / Edit buttons. Stack the actions on their
own row under the name + modified date, and pin the action buttons to
theme colors so the Edit link no longer renders link-blue.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CYa1RCQHxScbnkMG3UJZvR
@steezeburger steezeburger added the no-deploy Skip the production deploy when this PR merges label Oct 1, 2026 — with Claude
@steezeburger Claude

steezeburger commented Oct 1, 2026

Copy link
Copy Markdown
Owner Author

Deploy to Staging failed in staging-migrate: OperationalError: Temporary failure in name resolution connecting to this PR's freshly created staging Postgres. This PR only changes CSS, so it isn't the cause. It looks like the same first-deploy race PR #253 hit (run 765 failed, then the next deploy passed). There's no fix to port yet. Re-running the failed job once.

Generated by Claude Code

@steezeburger Claude

steezeburger commented Oct 1, 2026

Copy link
Copy Markdown
Owner Author

The re-run of Deploy to Staging failed earlier than the first run, before any deploy step ran: ssh: handshake failed: EOF after about 2 minutes, so the runner couldn't reach the staging VPS at all. Together with the DNS failure on the first run, this points to the staging host being unhealthy, possibly overloaded. Nothing in this CSS-only PR can fix that. I'm not re-running it again. The deploy needs someone with access to check the VPS and then re-trigger it.

Generated by Claude Code

@steezeburger steezeburger added the no-staging Skip staging deploys for this PR (leaves any running env alone) label Oct 1, 2026 — with Claude
@steezeburger steezeburger removed the no-deploy Skip the production deploy when this PR merges label Oct 1, 2026
@steezeburger
steezeburger merged commit 9acbff7 into main Oct 2, 2026
7 of 9 checks passed
@steezeburger
steezeburger deleted the ccr-10782aa9-uizgmo branch October 2, 2026 00:45

This branch was successfully deployed

1 active deployment
ci — 65d25341 Deployed Oct 2, 2026 by steezeburger via Teardown Staging #773
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

no-staging Skip staging deploys for this PR (leaves any running env alone)

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@steezeburger @claude