Skip to content

Add cgwalters-forge/misctool to the dispatch, fix and schedule bounds #690

Closed

Description

@cgwalters-bot

Part of #677. Make cgwalters-forge/misctool a repository that runs may target:

  • .github/agentic-job/dispatch.toml: repos, plus [unprotected_files].repos, so its first .github/ change (CI, review workflow) can be proposed. Per the comment there, the operator approves that change until misctool has a review workflow, as for agenthome.
  • .github/agentic-job/fix.toml: repos and [unprotected_files].repos, matching the dispatch list as poll.test.cjs checks.
  • .github/poll/agent-board.json: schedule.repositories. Not follow yet: like agenthome, it is followed only once it has a review workflow, and whether it gets the automatic merge is open (separate sub-issue).
  • The actions wrapper's bounds: check whether cgwalters-forge/actions (cgwalters-agentic-job.yml, workflow/*.toml) lists target repositories. If it does, note the change needed in the pull request; that edit belongs in actions.

Generated-by: https://github.com/cgwalters/#llms

Activity

  1. cgwalters-bot commented on Oct 17, 2026

    @cgwalters-bot
    CollaboratorAuthor
    {
      "brief": "Implement cgwalters-forge/tracker sub-issue of epic #677: add cgwalters-forge/misctool to .github/agentic-job/dispatch.toml (repos and [unprotected_files].repos), .github/agentic-job/fix.toml (repos and [unprotected_files].repos), and schedule.repositories in .github/poll/agent-board.json. Do not add it to `follow`. Keep the comments in those files accurate, update any tests that pin the lists (config.test.cjs, poll.test.cjs), and run them. Check whether cgwalters-forge/actions keeps its own list of target repositories. If it does, say so in the pull request description instead of guessing. The repository may not exist yet; listing it is inert until it does.",
      "item": 690,
      "kind": "implement",
      "repo": "cgwalters-forge/tracker",
      "runner": "hosted",
      "schema": "agent-board/job-plan/v1"
    }
    
  2. cgwalters-bot commented on Oct 17, 2026

    @cgwalters-bot
    CollaboratorAuthor

    Dispatched the plan in #690 (comment): run.

  3. github-actions commented on Oct 17, 2026

    @github-actions

    ✅ dispatch ended well and opened pull request #695. Result: #695

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions