Disable PR workflow for JP branches

[rucoder]

pull_request_target workflow is taken from a default branch however it must not be run for

• eve-kernel-arm64-v5.15.136-nvidia-jp6
• eve-kernel-arm64-v5.10.192-nvidia-jp5
• So disable it for these branches

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The negation pattern syntax used here will not work as intended in GitHub Actions. When using branches filter in pull_request_target, you cannot use negation patterns (with ! prefix) to exclude specific branches from a wildcard pattern.

The correct approach is to use branches-ignore alongside branches, or to specify explicit branch patterns. Consider one of these alternatives:

1. Use a combination of branches and branches-ignore (note they cannot be used together, so you'd need to rethink the filter strategy)
2. List all desired branches explicitly without wildcards
3. Use an if condition in the job level to check and skip the JP branches

For example, you could add a condition at the job level:

jobs:
  build:
    if: |
      !startsWith(github.event.pull_request.base.ref, 'eve-kernel-arm64-v5.15.136-nvidia-jp6') &&
      !startsWith(github.event.pull_request.base.ref, 'eve-kernel-arm64-v5.10.192-nvidia-jp5')

[rucoder]

@rene oh, GHA are SO limited... I have no good words...

[rene]

@rucoder , what about if we just set here eve-kernel-amd64-* instead of eve-kernel-* ?