Repository navigation
After each update, check which open issues and fixes apply to my machine #16333
Replies: 2 comments
|
Follow-up: I've built the smallest piece of this as a local script, and left out the GitHub posting for now. nixfred suggested building it as a separate plugin rather than an omarchy-doctor check, since Doctor stays local and offline. So I started with the part that needs no posting at all: telling me when an update undoes a PR patch I installed by hand.
On my ThinkPad P17 it's tracking #8560 and #14496. It hasn't seen a real update yet (I'm on 4.0.6), so the overwrite and merge paths are only tested against simulated files so far. I'll report back after the next update. The rest of the original idea (matching new issues to the machine profile, and agent-drafted test results) is still open. I'd still like to hear whether maintainers want hardware results posted to PRs that way before building it. |
|
Follow-up on What worked
What it got wrong
Channel note. 4.5.0 is on |
Uh oh!
There was an error while loading. Please reload this page.
I'd like feedback on an idea: a local agent check that runs after
omarchy update, finds the open issues and pending fixes that apply to my machine, and asks me to verify them. Anything it would post to GitHub is drafted for me to approve first.Why
On 2026-10-21 I tested several open PRs on my ThinkPad P17 Gen 1 (Omarchy 4.0.6, Quadro T1000 in discrete mode, S3 sleep) and posted results on each:
Window.activeguardTwo things will happen at the next update:
Many open issues (hybrid GPUs, s2idle, T2 Macs) can't affect this machine, and a few clearly can. Today I sort them by hand, and the record of what I tested is in my own notes.
How it would work
~/.config/omarchy/hooks/post-update.d/raises a notification. Clicking it opens the default agent withomarchy agent prompt, the same way the crash notification opensomarchy agent crash.sudo pacman -Qkk omarchy omarchy-settingsshows packaged files changed by hand (size or checksum mismatches; mtime-only changes are ignored). On my machine it finds the files both patches touched.Guardrails
diagnose-crash/reporting.md.Questions
default/agents/skills/plus apost-update.dhook the right shape if this ever goes into core, or is there a planned post-update notification to use instead?I've also asked @nixfred whether this fits as a check in omarchy-doctor, which already has a bar badge and an agent hand-off.
All reactions