Why: loading a page directly by URL shows "Page not found" for a moment before the page appears. The capability check probably finishes after the router has already resolved the catch-all route.
Done when: a direct load shows the loading state until capabilities are known, then the page, with no Page not found in between.
**Why**: loading a page directly by URL shows "Page not found" for a moment before the page appears. The capability check probably finishes after the router has already resolved the catch-all route.
**Done when**: a direct load shows the loading state until capabilities are known, then the page, with no Page not found in between.
sam
added the buglow labels 2026-11-22 00:20:22 +00: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.
Why: loading a page directly by URL shows "Page not found" for a moment before the page appears. The capability check probably finishes after the router has already resolved the catch-all route.
Done when: a direct load shows the loading state until capabilities are known, then the page, with no Page not found in between.