Skip to content

Owner question: update - a machine never quiet in its update hours: keep waiting or force after N days? #147

Open

Description

@scuttletoby

Recommendation: keep waiting and show it as "behind".

Context: update design for the fork. Keep the fork's updater (fork #5) until upstream's own lands, then take upstream's whole and keep three small add-ons: default stays OFF (fork #41, pinned by a test), an "update only between these hours" setting, and the existing quiet command. 7 PRs (+1 conditional).

The question: a machine is never quiet during its update hours. What then?

  • Keep waiting (recommended): it shows as "behind" and you update it by hand when it suits you; running agents are never stopped.
  • Update anyway after N days: it stays current, but running agents on that machine are stopped once.

Reply "keep waiting" or "after N days".

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions