Support pixel privacy review automation#33
Merged
Conversation
…l_task_id The composite action runs create-asana-task, which sets a `taskId` output on its inner step. Callers (per-repo privacy-review.yml workflows) had no way to read this — composite actions don't propagate inner step outputs unless declared. Expose them now so callers can chain follow-up automation like dispatching the AI Privacy Review classifier in duckduckgo/privacy-review-automation. - triage_task_id: GID of the Privacy Triage task this action just created - triage_task_permalink: built from the hardcoded project + the GID - original_task_id: GID matched from the PR description by find-asana-task-id No behavior change inside the action itself; outputs only. After merging, cut a new tag (eg. v2.4) so per-repo workflows can pin to the version that exposes these outputs. Co-authored-by: Cursor <cursoragent@cursor.com>
nshuba
approved these changes
May 15, 2026
Collaborator
nshuba
left a comment
There was a problem hiding this comment.
LGTM, but looks like there's a lint failure
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 79e3a27. Configure here.
nshuba
approved these changes
May 18, 2026
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.

https://app.asana.com/1/137249556945/project/1205243787707480/task/1214512208674130?focus=true
The composite action runs create-asana-task, which sets a
taskIdoutput on its inner step. Callers (per-repo privacy-review.yml workflows) had no way to read this — composite actions don't propagate inner step outputs unless declared. Expose them now so callers can chain follow-up automation like dispatching the AI Privacy Review classifier in duckduckgo/privacy-review-automation.No behavior change inside the action itself; outputs only.
After merging, cut a new tag (eg. v2.4) so per-repo workflows can pin to the version that exposes these outputs.
Note
Medium Risk
Introduces a new cross-repo
workflow_dispatchcall that depends ongithub_patpermissions and a non-mainworkflow ref, which could trigger unintended automation if misconfigured.Overview
After creating the Asana privacy triage task, the composite action now dispatches the
privacy-review-classifier.lock.ymlworkflow induckduckgo/privacy-review-automation, passingpr_urland the createdprivacy_triage_task_id.Also bumps this package/action version from
1.3.0to2.4.0inpackage.jsonandpackage-lock.json.Reviewed by Cursor Bugbot for commit 12bd807. Bugbot is set up for automated code reviews on this repo. Configure here.