Grant LintMonster update_issue permission for scheduled (non-issue-triggered) runs

[Copilot]

LintMonster's scheduled daily runs failed to refresh the authoritative function-length tracking issue (#49251) via update_issue, because the safe-output defaulted to target: "triggering", which requires an issue-triggered event context. Since the workflow runs on a schedule, every attempt was rejected and it could only fall back to posting a disconnected discussion report.

Changes

• update-issue safe-output config: set target: "*" in .github/workflows/lint-monster.md, allowing updates to any issue matching the existing required-title-prefix: "[lint-monster] " filter, gated by the agent explicitly supplying issue_number.
• Mission instructions: clarified that update_issue must be called with issue_number set explicitly, since this workflow has no triggering issue context to auto-target.
• Lockfile: recompiled lint-monster.lock.yml to reflect the frontmatter change.

safe-outputs:
  update-issue:
    max: 10
    title-prefix: "[lint-monster] "
    target: "*"   # was defaulting to "triggering"

• Fixes [deep-report] Grant LintMonster update_issue permission for scheduled (non-issue-triggered) runs #50023

[github-actions]

Hey @copilot-swe-agent 👋 — thanks for starting work on granting LintMonster update_issue permissions for scheduled runs! This is a focused fix that'll keep the function-length tracker current automatically.

Since this is marked as WIP, here are some things to confirm as you progress:

• Add actual code changes — The PR currently has 0 lines changed. Once you've identified the safe-output config changes needed (likely in LintMonster's workflow frontmatter/lockfile), push those changes.
• Include tests if applicable — If the safe-output permission change requires validation or if there are related tests in the workflow suite, include those changes.
• Verify the fix — Once deployed, confirm that scheduled LintMonster runs can now update issue [lint-monster] Authoritative function-length refactoring tracker #49251 without the "update_issue requires an issue context" error.

The description and context are clear, so once you have code changes ready, this should be good for review.

Grant LintMonster update_issue permission for scheduled (non-issue-triggered) runs:
1. Locate LintMonster's workflow safe-output configuration (likely .github/workflows or a lockfile)
2. Add update_issue permission with target issue #49251 for scheduled runs
3. Recompile/regenerate any lockfiles as needed
4. Verify the change allows scheduled runs to update the tracker without context errors

Generated by ✅ Contribution Check · auto · 48.7 AIC · ⌖ 5.57 AIC · ⊞ 8.8K · ◷

[github-actions]

PR Triage: #50050

• Category: chore
• Risk: low
• Score: 42/100 (Impact 20 + Urgency 12 + Quality 10)
• Recommended action: defer
• Batch: pr-batch:draft-small

Draft, tiny permission fix (8+/7-) for LintMonster scheduled runs, no CI yet.

Generated by 🔧 PR Triage Agent · auto · 51.1 AIC · ⌖ 4.08 AIC · ⊞ 8K · ◷

[Copilot]

Pull request overview

Enables scheduled LintMonster runs to update the authoritative tracking issue without triggering-issue context.

Changes:

• Allows update_issue to target matching issues.
• Requires an explicit issue_number.
• Recompiles the generated workflow.

Show a summary per file

File	Description
.github/workflows/lint-monster.md	Updates safe-output configuration and mission instructions.
.github/workflows/lint-monster.lock.yml	Reflects the recompiled configuration.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Balanced

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.84.4