Suppress no-op tracking issue posts from bump-tcgc-csharp workflow#10517
Open
Suppress no-op tracking issue posts from bump-tcgc-csharp workflow#10517
Conversation
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>
Copilot created this pull request from a session on behalf of
jorgerangel-msft
April 27, 2026 22:31
View session
Contributor
There was a problem hiding this comment.
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-csharpworkflow viasafe-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". |
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>
Collaborator
|
You can try these changes here
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The daily
bump-tcgc-csharpagentic 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 settingsafe-outputs.noop.report-as-issue: false..github/workflows/bump-tcgc-csharp.lock.yml— Updated to reflect the source change:noophandler config blobs flipreport-as-issuefrom"true"to"false".GH_AW_NOOP_REPORT_AS_ISSUEenv var on theProcess no-op messagesstep in theconclusionjob flipped from"true"to"false". This is the env var actually consumed byhandle_noop_message.cjsto decide whether to post to the[aw] No-Op Runstracking issue, and was the reason a follow-up run ([aw] No-Op Runs #10518) was still posting after the initial fix.