Skip to content

Publish the ABI check comment and labels via - #3276

Open
fujitatomoya wants to merge 1 commit into
rollingfrom
abi-report-workflow-run
Open

fujitatomoya wants to merge 1 commit into
rollingfrom
abi-report-workflow-run

Conversation

@fujitatomoya

@fujitatomoya fujitatomoya commented Sep 17, 2026

Copy link
Copy Markdown
Collaborator

Description

shoudl close fujitatomoya/ros2-abi-action#13

Follow-up to #3262. Publish the ABI check's sticky comment and the ABI compatible / ABI break label from a workflow_run workflow so that pull requests from forks get them as well.

Problem.
The abi workflow itself runs fine on fork pull requests (see #3268: all four libraries were diffed and reported compatible), but the comment and the label never appeared. On pull_request events from a fork, GitHub gives the job a read-only GITHUB_TOKEN regardless of the permissions: block, so every write failed with Resource not accessible by integration (visible as warnings in the diff job logs). Since nearly every rclcpp pull request comes from a fork, the label was effectively never applied.

Fixes # (issue)

Is this user-facing behavior change?

Yes, forked PR can also comment about the abi-compliance result.

Did you use Generative AI?

Yes, Claude Fable 5.1

Additional Information

Signed-off-by: Tomoya.Fujita <fujita.tomoya@triorb.co.jp>

@fujitatomoya fujitatomoya left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@ahcorde can you approve this?

note that, ABI compliance check is still in the test flight. i want see if it works for everyone including forked PR to put the compliance check comment and label after this PR is merged.

Comment on lines +5 to +11
# This is a separate workflow because abi.yaml builds and diffs the pull
# request's own code. For pull requests from forks GitHub therefore runs it
# with a read-only token, whatever permissions it asks for, and it cannot
# write to the PR. workflow_run workflows instead run the workflow file from
# the default branch of this repository with a normal token; this one never
# checks out or executes anything from the pull request, it only downloads the
# report artifacts the abi run uploaded and posts what they say.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

this is exactly what this PR trying to solve.

@fujitatomoya fujitatomoya self-assigned this Sep 17, 2026
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.

PR comes from the fork is unable to tag the lable

1 participant