Skip to content

chore(ci): fix /component-test backward compat with older PR branches#21907

Merged
gnodet merged 1 commit intomainfrom
ci/fix-component-test-compat
Mar 10, 2026
Merged

chore(ci): fix /component-test backward compat with older PR branches#21907
gnodet merged 1 commit intomainfrom
ci/fix-component-test-compat

Conversation

@gnodet
Copy link
Contributor

@gnodet gnodet commented Mar 10, 2026

Summary

Fixes Missing either 'issue-number' or 'comment-id' error when /component-test runs against PRs created before #21906.

The workflow runs from main but the component-test action is loaded from the PR branch checkout. Old PR branches still have the action.yaml that requires comment-id as a mandatory input, but #21906 stopped passing it.

  • Pass comment-id from the workflow (ignored by the new action, needed by old branches)
  • Keep comment-id as an optional input in the action for backward compatibility

…ranches

The workflow runs from main but the component-test action is loaded from
the PR branch checkout. Old PR branches still have the action.yaml that
requires comment-id as input. Pass comment-id from the workflow and keep
it as an optional input in the action for backward compatibility.
@gnodet gnodet merged commit 52d9612 into main Mar 10, 2026
2 checks passed
@github-actions
Copy link
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

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.

1 participant