Skip to content

github: Make posting image change reports to a PR non-fatal - #4315

Merged
chewi merged 1 commit into
mainfrom
chewi/non-fatal-pr-reports
Oct 9, 2026
Merged

chewi merged 1 commit into
mainfrom
chewi/non-fatal-pr-reports

Conversation

@chewi

@chewi chewi commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

This is currently failing following the Linux 6.18 bump because the changes are too large for the GitHub API.

This is currently failing following the Linux 6.18 bump because the
changes are too large for the GitHub API.

Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
@chewi chewi self-assigned this Oct 9, 2026
Copilot AI balanced review requested due to automatic review settings October 9, 2026 15:16
@chewi
chewi requested a review from a team as a code owner October 9, 2026 15:16

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Approval recommended

The focused workflow change matches the stated intent without masking build or artifact-upload failures.

0 open findings

What changed in this PR

Makes oversized PR image-change reports non-fatal while retaining uploaded report artifacts.

Changes:

  • Allows CI to continue if posting a report comment fails.
File Description
.github/​workflows/​ci.yaml Marks the PR report-posting step as non-fatal.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@chewi
chewi merged commit d50789d into main Oct 9, 2026
3 of 4 checks passed
@chewi
chewi deleted the chewi/non-fatal-pr-reports branch October 9, 2026 15:28

This branch is waiting to be deployed

1 waiting deployment
development — bb36689b Waiting Oct 9, 2026 by chewi via Wait for approval #5988
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants