Skip to content

Suppress no-op tracking issue posts from bump-tcgc-csharp workflow#10517

Open
Copilot wants to merge 2 commits intomainfrom
copilot/update-workflow-to-prevent-issue-creation
Open

Suppress no-op tracking issue posts from bump-tcgc-csharp workflow#10517
Copilot wants to merge 2 commits intomainfrom
copilot/update-workflow-to-prevent-issue-creation

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 27, 2026

The daily bump-tcgc-csharp agentic workflow posts to the No-Op tracking issue (#10516) on every run where no newer stable TCGC release is available, which is the common case and creates noise.

Changes

  • .github/workflows/bump-tcgc-csharp.md — Opt out of no-op reporting by setting safe-outputs.noop.report-as-issue: false.
  • .github/workflows/bump-tcgc-csharp.lock.yml — Updated to reflect the source change:
    • Embedded noop handler config blobs flip report-as-issue from "true" to "false".
    • GH_AW_NOOP_REPORT_AS_ISSUE env var on the Process no-op messages step in the conclusion job flipped from "true" to "false". This is the env var actually consumed by handle_noop_message.cjs to decide whether to post to the [aw] No-Op Runs tracking issue, and was the reason a follow-up run ([aw] No-Op Runs #10518) was still posting after the initial fix.
safe-outputs:
  messages:
    footer: ">  Generated by [{workflow_name}]({run_url})"
    footer-install: "<!-- -->"
  noop:
    report-as-issue: false
  create-issue:
    ...

Agent-Logs-Url: https://github.com/microsoft/typespec/sessions/6457c89b-e5c1-43b6-b779-1e16c4ad1e82

Co-authored-by: jorgerangel-msft <102122018+jorgerangel-msft@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Reduces noise from the daily bump-tcgc-csharp agentic workflow by suppressing no-op run reporting to the repository’s no-op tracking issue (#10516).

Changes:

  • Disabled no-op “report as issue” behavior for the bump-tcgc-csharp workflow via safe-outputs.noop.report-as-issue: false.
  • Regenerated the compiled lock workflow to reflect the updated safe-outputs no-op handler configuration.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/bump-tcgc-csharp.md Adds safe-outputs.noop.report-as-issue: false to opt out of posting no-op runs to the tracking issue.
.github/workflows/bump-tcgc-csharp.lock.yml Regenerated compiled workflow; updates embedded safe-outputs handler config to set report-as-issue to "false".

Comment thread .github/workflows/bump-tcgc-csharp.md
Agent-Logs-Url: https://github.com/microsoft/typespec/sessions/c9ccc6b2-7f8f-464f-b71f-f76da003dbec

Co-authored-by: jorgerangel-msft <102122018+jorgerangel-msft@users.noreply.github.com>
@azure-sdk
Copy link
Copy Markdown
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants