ci: skip integration test on release-please PRs

[venkatamutyala]

What

Adds paths-ignore to the Integration Test pull_request trigger so it doesn't run on release-please's release PR:

on:
  pull_request:
    types: [opened, synchronize, reopened]
    paths-ignore:
      - 'CHANGELOG.md'
      - '.release-please-manifest.json'
  push:
    branches: [main]

Why

release-please's release PR (e.g. #143) is authored by github-actions[bot] and only ever edits CHANGELOG.md and .release-please-manifest.json. Because the repo/org's "outside contributor" Actions policy gates bot-authored PRs behind a manual Approve and run, every release PR has been requiring a manual click to run CI.

Path filters are evaluated before the run is created, so a PR that touches only these two files produces no run — and there's nothing to approve. (A job-level if: wouldn't help: the run would still be created in action_required first.)

Impact

• ✅ No more manual approvals for release PRs.
• ✅ Real PRs (changing action.yml, tests, README, etc.) still trigger CI normally.
• ⚠️ The release PR itself gets no CI — acceptable, since it contains only auto-generated changelog/version content, not action code.
• A human PR that happens to touch only CHANGELOG.md would also skip CI, which is fine.

Note

This is the lightweight fix. The alternative (a GitHub App token for release-please) also removes the gate and additionally lets release events trigger downstream workflows — worth revisiting if release automation gets standardized across GlueOps repos, but it needs org-owner setup and isn't needed for this repo today.

[github-actions]

⬇️ Download the full plan (tofu-plan.txt): https://github.com/GlueOps/github-actions-opentofu-continuous-delivery/actions/runs/28247091011/artifacts/7909154247

OpenTofu Plan

Show plan

OpenTofu used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

OpenTofu will perform the following actions:

  # null_resource.integration_test will be created
  + resource "null_resource" "integration_test" {
      + id = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + ok = "integration-test"