the container that holds entrypoints and columns on the hook page is rather narrow, and causes the webhook url to wrap. i'm using it on a big monitor in landscape and there are huge white margins on both sides. can we expand its width by 50-100%?
Definition of done, on a webhook's page:
The container holding the entrypoints and the columns beside them is 50-100% wider on large screens than today (the PR states the old and new maximum widths).
On a 1920-pixel-wide window the entrypoint's webhook URL fits on one line without wrapping.
Narrow screens are unchanged: at phone width the page has no horizontal scrolling and reads as before.
If other pages share the same container, the PR says whether they widened too and why; they must not break.
A browser check (headless Chrome at 1920 and at phone width) confirms both.
Model: opus-5-5
sneak, 2026-09-29 in chat (verbatim):
> the container that holds entrypoints and columns on the hook page is rather narrow, and causes the webhook url to wrap. i'm using it on a big monitor in landscape and there are huge white margins on both sides. can we expand its width by 50-100%?
Definition of done, on a webhook's page:
- The container holding the entrypoints and the columns beside them is 50-100% wider on large screens than today (the PR states the old and new maximum widths).
- On a 1920-pixel-wide window the entrypoint's webhook URL fits on one line without wrapping.
- Narrow screens are unchanged: at phone width the page has no horizontal scrolling and reads as before.
- If other pages share the same container, the PR says whether they widened too and why; they must not break.
- A browser check (headless Chrome at 1920 and at phone width) confirms both.
Model: opus-5-5
clawbot
self-assigned this 2026-09-29 11:37:07 +02:00
Plan. The webhook page is templates/source_detail.html, whose outer container is max-w-6xl (72rem, 1152 px). templates/base.html, templates/navbar.html, the webhook list and the event log use the same width.
Widen: raise the webhook page's own container by 50-100%, so 1728-2304 px (max-w-screen-2xl is only 1536 px, +33%, which is too little). Check the arithmetic, and state the old and new widths on the PR.
Layout wrapper: if base.html's wrapper caps the page first, widen that too. Say which other pages widen as a result, and check that they do not break.
Styling:static/css/tailwind.css is the compiled Tailwind stylesheet and is committed. A class the page uses must already be in that file. If it is not, prefer a small plain rule in static/css/style.css. Regenerate tailwind.css only through make css, and disclose it on the PR if you do (the unpinned tool is #231).
Browser checks: headless Chrome in a container, with a small data set built in batches (the standing RAM cap), the container named with webhooker and your role, removed afterwards. Publish no screenshots or logs on the tracker.
templates/source_detail.html is also touched by #347, in the recent-events section. Whichever lands second rebases.
Model: opus-5-5
Plan. The webhook page is `templates/source_detail.html`, whose outer container is `max-w-6xl` (72rem, 1152 px). `templates/base.html`, `templates/navbar.html`, the webhook list and the event log use the same width.
- **Widen:** raise the webhook page's own container by 50-100%, so 1728-2304 px (`max-w-screen-2xl` is only 1536 px, +33%, which is too little). Check the arithmetic, and state the old and new widths on the PR.
- **Layout wrapper:** if `base.html`'s wrapper caps the page first, widen that too. Say which other pages widen as a result, and check that they do not break.
- **Styling:** `static/css/tailwind.css` is the compiled Tailwind stylesheet and is committed. A class the page uses must already be in that file. If it is not, prefer a small plain rule in `static/css/style.css`. Regenerate `tailwind.css` only through `make css`, and disclose it on the PR if you do (the unpinned tool is https://git.eeqj.de/sneak/webhooker/issues/231).
- **Browser checks:** headless Chrome in a container, with a small data set built in batches (the standing RAM cap), the container named with `webhooker` and your role, removed afterwards. Publish no screenshots or logs on the tracker.
- `templates/source_detail.html` is also touched by https://git.eeqj.de/sneak/webhooker/issues/347, in the recent-events section. Whichever lands second rebases.
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):
Definition of done, on a webhook's page:
Model: opus-5-5
Plan. The webhook page is
templates/source_detail.html, whose outer container ismax-w-6xl(72rem, 1152 px).templates/base.html,templates/navbar.html, the webhook list and the event log use the same width.max-w-screen-2xlis only 1536 px, +33%, which is too little). Check the arithmetic, and state the old and new widths on the PR.base.html's wrapper caps the page first, widen that too. Say which other pages widen as a result, and check that they do not break.static/css/tailwind.cssis the compiled Tailwind stylesheet and is committed. A class the page uses must already be in that file. If it is not, prefer a small plain rule instatic/css/style.css. Regeneratetailwind.cssonly throughmake css, and disclose it on the PR if you do (the unpinned tool is #231).webhookerand your role, removed afterwards. Publish no screenshots or logs on the tracker.templates/source_detail.htmlis also touched by #347, in the recent-events section. Whichever lands second rebases.Model: opus-5-5