Repository navigation
Conversation
[Low impact] This documentation-only PR appears safe to merge. SummaryThis documentation-only PR brings hook and orphan-cleanup descriptions closer to the current code.
Reviews (2) · Last reviewed commit: "Describe update hooks as sharing ordinar..." · Reviewed by Greptile |
|
I checked each statement in this change against A second review by Codex at medium effort checked the same claims against the code and found nothing wrong. It also could read this session's working notes, so it may not have been fully independent. One thing for the maintainer: #14914 changes the code the other way. It ends the update's authorization before |
quattro now uses ordinary sudo (omacom#17000) and runs AUR updates under the update's one authorization (omacom#16568), and its hooks.md already describes that. Keep quattro's paragraph there and this branch's corrected post-update tree comment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Since omacom#17000 neither omarchy update nor omarchy refresh pacman clears its sudo timestamp, and AUR updates share the update's one authorization (omacom#16568), so nothing is cleared before AUR and a hook's sudo can reuse what was already asked for. It can, not does: a standalone refresh has no keepalive, so a hook that waits past the ten-minute timestamp prompts again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex Medium <noreply@openai.com>
|
This had stopped merging after
Every statement was checked against Codex Medium and muse-wonder (via pi, thinking high) reviewed the port. Codex found that my first wording, "doesn't ask again", was too absolute for a standalone refresh, and that is what the "can" fixes. The second round, on the current head |
The hook documentation says cached sudo authorization is cleared before both update hooks. The implementation runs
post-updatewhile update authorization remains active;pre-refresh-pacmanruns before that authorization starts.Describe those boundaries consistently in the manual and agent hook guide. Also align the stale design decision with the automatic orphan cleanup deliberately introduced by #14428.
Validation: compared the documented order with the current update implementation and sudo policy; all 117 CLI checks pass. This changes documentation only.
Addresses the documentation finding in review #9454.