Use head ref for PRs

[nick-fields]

When triggering CircleCI pipelines on PR events, the branch that is sent to CCI is refs/pull/<pr#> but nobody needs/cares about that ref. Instead the head ref should be sent which is the branch name (minus refs/heads) that is being merged into the PR base branch.

[nick-fields]

This will also resolve #13

[aalong-tr]

Thank you for writing this! I hope it gets merged, as this change is vital to my primary use-case for this action.

[paynerc]

I am also following this... I need to be able to add comments to PRs that trigger GH actions that start a CirlceCI pipeline, but currently it always runs against main.

[nghiadoan91]

I hope this merged soon, Im using github label to trigger in the PR

[tmountjr]

I had some problems in #18 that this could potentially resolve as well.

[Irvenae]

can this be merged please?

[Irvenae]

can this be merged please?

[tmountjr]

@KyleTryon saw that you have occasionally merged PRs in the past - would you be able to review this and provide feedback?

[nick-fields]

I'm not sure how long CircleCI takes to merge these kinds of things. Feel free to use my fork if you need something immediately, I've been using it in production for 6wks with no issues. It's worth noting I removed the GHA_Meta inputs as I didn't find value in them, see commit.

on:
  pull_request:
    types: [opened, reopened]

jobs:
  trigger-circleci:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger CircleCI build
        uses: nick-fields/trigger-circleci-pipeline-action@57c093b9d0d06d35f0107ae1fb3957ef3960aaed
        env:
          CCI_TOKEN: ${{ secrets.CIRCLECI_API_TOKEN }}

[tmountjr]

@nick-fields good to know because I actually was planning on passing metadata to circle ci that way. 😬

[nick-fields]

@tmountjr in that case, you can just use the sha of the commit in this PR:

on:
  pull_request:
    types: [opened, reopened]

jobs:
  trigger-circleci:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger CircleCI build
        uses: nick-fields/trigger-circleci-pipeline-action@dd5d85644c1e65f107ecb7f34402c2825b2e418d
        env:
          CCI_TOKEN: ${{ secrets.CIRCLECI_API_TOKEN }}

[Irvenae]

you can just use CircleCI-Public/trigger-circleci-pipeline-action@dd5d85644c1e65f107ecb7f34402c2825b2e418d btw

[KyleTryon]

Hell all, sorry for the delay! This is being merged and deployed right now. We'll be live in a few moments. Thank you @nick-fields