Problem description
The campaign-release-info workflow uses github-actions[bot] as commit author, which is rejected by EasyCLA because this bot identity is not on the CAMARA EasyCLA allowlist.
Example: camaraproject/QualityOnDemand#508 (comment)
Expected behavior
Campaign commits should use hdamker-bot identity which is known to EasyCLA and will pass CLA checks.
Change in actions/campaign-finalize-per-repo/action.yml lines 216-217:
# Current:
git config user.name "github-actions[bot]"
git config user.email "github-actions[bot]@users.noreply.github.com"
# Change to:
git config user.name "hdamker-bot"
git config user.email "hdamker-bot@users.noreply.github.com"
Alternative solution
Request Linux Foundation to add github-actions[bot] to CAMARA EasyCLA allowlist (similar to OpenTelemetry community issue #809). This is a longer-term solution that would benefit all CAMARA workflows using GITHUB_TOKEN.
Additional context
This issue blocks the full rollout of the release information sync campaign. Test PRs created in QoSBooking #74 and QualityOnDemand #510 need to be recreated to pass EasyCLA checks once this change is deployed.
Problem description
The campaign-release-info workflow uses
github-actions[bot]as commit author, which is rejected by EasyCLA because this bot identity is not on the CAMARA EasyCLA allowlist.Example: camaraproject/QualityOnDemand#508 (comment)
Expected behavior
Campaign commits should use hdamker-bot identity which is known to EasyCLA and will pass CLA checks.
Change in actions/campaign-finalize-per-repo/action.yml lines 216-217:
Alternative solution
Request Linux Foundation to add
github-actions[bot]to CAMARA EasyCLA allowlist (similar to OpenTelemetry community issue #809). This is a longer-term solution that would benefit all CAMARA workflows using GITHUB_TOKEN.Additional context
This issue blocks the full rollout of the release information sync campaign. Test PRs created in QoSBooking #74 and QualityOnDemand #510 need to be recreated to pass EasyCLA checks once this change is deployed.