Skip to content

Remove DASH review token - #235

Open
umaucher wants to merge 1 commit into
mainfrom
um-remove-dash-review-token
Open

umaucher wants to merge 1 commit into
mainfrom
um-remove-dash-review-token

Conversation

@umaucher

Copy link
Copy Markdown
Contributor

Remove the DASH API-token requirement from the reusable license-check workflow.

DASH license validation and the existing PR result comment work without a token. The token was used only by dash-licenses -review to create Eclipse IP Team review requests automatically.

Those requests are an asynchronous escalation and should be started deliberately when a maintainer decides follow-up is needed. The result comment now links to the DASH manual review-request instructions.

Validation:

  • bazel run --lockfile_mode=error //:license-check -- -project automotive.score -repo https://github.com/eclipse-score/persistency (passes; DASH reported review findings without a token)
  • git diff --check

Follow-up: consumers can remove their dash-api-token secret mapping when updating to this workflow revision.

DASH license validation and result comments do not require the API token. The token was used only by dash-licenses' -review option to open Eclipse IP Team review requests automatically.\n\nAutomatic review creation is intentionally removed from every CI run: it is an asynchronous escalation that may take time and needs a maintainer decision. The PR comment now links to DASH's manual review-request instructions for cases that need follow-up.

Signed-off-by: Uwe Maucher <205777204+umaucher@users.noreply.github.com>
@AlexanderLanin

Copy link
Copy Markdown
Member

cant we fix the token? automatic review trigger was actually intentional. As we should actually wait for approval before merging.

@umaucher

umaucher commented Sep 16, 2026

Copy link
Copy Markdown
Contributor Author

cant we fix the token? automatic review trigger was actually intentional. As we should actually wait for approval before merging.

maybe the better approach

have the secret optional so we can clarify why the org secret is not working but still have the check reporting the correct commend if needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants