[BUG] CI: `automatic-merges` fails on every PR
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Start with the automatic-merges workflow and the linked failing job, then inspect the GitHub App token step and how its client ID is provided. Reproduce by creating or updating a pull request. Done means the workflow receives a non-empty client ID and the automatic-merges CI job no longer fails.
Written by the indexing model from the issue text.
Description
What is the bug?
every time i create a PR (or update a PR) the automatic-merges workflow runs and fails
example job: https://github.com/opensearch-project/security/actions/runs/33604107797/job/100164094477
the "GitHub App token" step is always failling:
Warning: Input 'app-id' has been deprecated with message: Use 'client-id' instead.
Run actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1
Error: The 'client-id' (or deprecated 'app-id') input must be set to a non-empty string. If using a secret or variable, ensure it is available in this workflow context.
at run (/home/runner/work/_actions/actions/create-github-app-token/bcd2ba49218906704ab6c1aa796996da409d3eb1/dist/main.cjs:23425:11)
at Object.<anonymous> (/home/runner/work/_actions/actions/create-github-app-token/bcd2ba49218906704ab6c1aa796996da409d3eb1/dist/main.cjs:23449:20)
at Module._compile (node:internal/modules/cjs/loader:1872:14)
at Object..js (node:internal/modules/cjs/loader:2003:10)
at Module.load (node:internal/modules/cjs/loader:1594:32)
at Module._load (node:internal/modules/cjs/loader:1396:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47
Error: The 'client-id' (or deprecated 'app-id') input must be set to a non-empty string. If using a secret or variable, ensure it is available in this workflow context.
How can one reproduce the bug?
create a PR (or push a changed/new commit to one)
What is the expected behavior?
no failing CI jobs
What is your host/environment?
n/a
Do you have any screenshots?
n/a
Do you have any additional context?
n/a
- Dominant language
- Java
- Stars
- 252
- Forks
- 395
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 74
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opensearch-project/security
-
bug untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opensearch-project/security#6524 ·
-
bug triaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
opensearch-project/security#6105 · 3 comments ·
-
bug triaged
Difficulty 1/5 Under an hour Newbie friendliness 72/100
opensearch-project/security#6103 · 4 comments ·
-
triaged
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
opensearch-project/security#5075 · 1 comment ·
-
duplicate enhancement untriaged
Difficulty 5/5 Over a week Newbie friendliness 25/100
opensearch-project/security#6544 · 1 comment ·
All issues in opensearch-project/security
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100