Lets the brencher UI pre-fill its branch filter from a ?filter=<text> query
parameter on initial page load.
Use case
Deep-link filtered views from external tooling (runbooks, Gitea issues,
dashboards). For example:
https://brencher.rudolf.keenetic.link/?filter=connectivity_tester — go straight to the new stack after #65 lands.
https://brencher.rudolf.keenetic.link/?filter=hermes_infra%20v0.4.0 — multiple words (current filter does substring match on all).
Changes
frontend/app.js: IIFE on initial load reads URLSearchParams, sets branchFilter.value, calls filterBranches(). Empty / missing param
leaves the filter empty (no pre-fill, no apply) — same as before.
Acceptance
?filter=foo pre-fills the input AND applies the filter on initial render.
Empty ?filter= is a no-op (param present but empty string).
No param at all is a no-op (no pre-fill, no apply).
Existing inline typing behaviour unchanged.
Resolves
admin/brencher#66 (brencher UI: support ?filter= GET-param that auto-fills the filter input)
Related
admin/brencher#65 (PR feat(configs): add connectivity_tester stack) — once #65 merges, the link /<brencher-host>/?filter=connectivity_tester becomes a one-click entry point to the new stack.
## Summary
Lets the brencher UI pre-fill its branch filter from a `?filter=<text>` query
parameter on initial page load.
## Use case
Deep-link filtered views from external tooling (runbooks, Gitea issues,
dashboards). For example:
- `https://brencher.rudolf.keenetic.link/?filter=connectivity_tester` — go straight to the new stack after #65 lands.
- `https://brencher.rudolf.keenetic.link/?filter=hermes_infra%20v0.4.0` — multiple words (current filter does substring match on all).
## Changes
`frontend/app.js`: IIFE on initial load reads `URLSearchParams`, sets
`branchFilter.value`, calls `filterBranches()`. Empty / missing param
leaves the filter empty (no pre-fill, no apply) — same as before.
## Acceptance
- `?filter=foo` pre-fills the input AND applies the filter on initial render.
- Empty `?filter=` is a no-op (param present but empty string).
- No param at all is a no-op (no pre-fill, no apply).
- Existing inline typing behaviour unchanged.
## Resolves
- admin/brencher#66 (brencher UI: support ?filter=<text> GET-param that auto-fills the filter input)
## Related
- admin/brencher#65 (PR feat(configs): add connectivity_tester stack) — once #65 merges, the link `/<brencher-host>/?filter=connectivity_tester` becomes a one-click entry point to the new stack.
Lets operators deep-link a filtered view, e.g. /?filter=connectivity_tester
from a Gitea issue body, dashboard, or runbook. The value is applied
immediately on initial render via filterBranches().
Empty / missing param leaves existing behaviour unchanged.
Resolvesadmin/brencher#66.
admin
merged commit 2e48d11b77 into main2026-09-14 18:43:07 +02:00
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.
Summary
Lets the brencher UI pre-fill its branch filter from a
?filter=<text>queryparameter on initial page load.
Use case
Deep-link filtered views from external tooling (runbooks, Gitea issues,
dashboards). For example:
https://brencher.rudolf.keenetic.link/?filter=connectivity_tester— go straight to the new stack after #65 lands.https://brencher.rudolf.keenetic.link/?filter=hermes_infra%20v0.4.0— multiple words (current filter does substring match on all).Changes
frontend/app.js: IIFE on initial load readsURLSearchParams, setsbranchFilter.value, callsfilterBranches(). Empty / missing paramleaves the filter empty (no pre-fill, no apply) — same as before.
Acceptance
?filter=foopre-fills the input AND applies the filter on initial render.?filter=is a no-op (param present but empty string).Resolves
Related
/<brencher-host>/?filter=connectivity_testerbecomes a one-click entry point to the new stack.