Skip to content

Conversation

polasudo
Copy link
Contributor

When running the /publish action in a PR and the Backstage compatibility check fails, retrieve the markdown artifact and add it as a PR comment instead of requiring users to navigate to the workflow run to see the compatibility results.

This reuses the existing backstage-compatibility-report.md artifact from the check-backstage-compatibility workflow.

Jira

…ailure

When running the /publish action in a PR and the Backstage compatibility check fails,
retrieve the markdown artifact and add it as a PR comment instead of requiring
users to navigate to the workflow run to see the compatibility results.

This reuses the existing backstage-compatibility-report.md artifact from the
check-backstage-compatibility workflow.
@polasudo
Copy link
Contributor Author

/publish

Copy link
Contributor

PR action (/publish) cancelled: PR doesn't touch only 1 workspace.

@polasudo polasudo marked this pull request as ready for review October 13, 2025 12:40
@polasudo polasudo requested review from a team, gashcrumb and kadel as code owners October 13, 2025 12:41
@github-actions github-actions bot added the non-workspace-changes PR changes files outside workspace directories label Oct 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

non-workspace-changes PR changes files outside workspace directories

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant