[BUG] CI: `automatic-merges` fails on every PR

[rursprung]

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

[cwperks]

Ty for filing this @rursprung . At one point we had the repo configured to automatically merge dependabot PRs and documentation PRs after necessary approvals. I do think we should get that working together...but only after maintainer approval.

[rursprung]

if you anyway approve a PR - why not hit the merge button manually as well? i don't quite see the need for an automation in that case (unless you'd want to approve & merge it automatically, which - understandably - isn't the case here).

since the workflow is always failing i'd suggest to delete it for now and create a follow-up issue. you can always restore the last version from git when you get around to fixing it. currently everyone working on PRs always gets failed workflow runs because of this.