fix(ci): explicitly define secrets in reusable workflows #961
Conversation
Resolves the "Unrecognized named-value: 'secrets'" validation error in GitHub Actions. Reusable workflows triggered via `workflow_call` must explicitly declare the secrets they expect to receive, even when `secrets: inherit` is used by the caller. Updates: - .github/workflows/gemini-triage.yml - .github/workflows/gemini-review.yml - .github/workflows/gemini-invoke.yml
|
🤖 Hi @awaemmanuel, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
|
🤖 I'm sorry @awaemmanuel, but I was unable to process your request. Please see the logs for more details. |
|
🤖 Hi @awaemmanuel, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
|
🤖 I'm sorry @awaemmanuel, but I was unable to process your request. Please see the logs for more details. |
|
@gemini-cli /review |
|
🤖 Hi @awaemmanuel, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
|
@gemini-cli /review again please |
|
🤖 Hi @awaemmanuel, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
|
@gemini-cli /review |
|
🤖 Hi @awaemmanuel, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
1 participant
Resolves the "Unrecognized named-value: 'secrets'" validation error in GitHub Actions. Reusable workflows triggered via
workflow_callmust explicitly declare the secrets they expect to receive, even whensecrets: inheritis used by the caller. Updates:Pull-Request Template
Thank you for your contribution! Please provide a brief description of your changes and ensure you've completed the checklist below.
Description
What does this PR do?
Why is it necessary?
Fixes # (if applicable)
Checklist
nox -s formatto format the code.aaie_notebook_template.ipynbif submitting a new jupyter notebook.