feat: add git_resources input for per-step Git resource refs (SF-2251)

[NickJosevski]

Draft — source-only for review. Depends on OctopusDeploy/api-client.ts#280. Dependency bump + dist rebuild are deferred to ready-time (see "Landing" below), which is why this diff is just the 12-line source change and no regenerated bundle.

What

Adds a new git_resources action input that lets a release target a specific Git reference for a step's Git resource at release-creation time.

Format (multi-line, mirrors the Octopus CLI --git-resource flag):

- uses: OctopusDeploy/create-release-action@v4
  with:
    project: "My Argo Project"
    git_resources: |
      Update Argo CD Application Manifests:${{ github.head_ref || github.ref_name }}

StepName:GitRef or StepName:GitResourceName:GitRef.

Why

For version-controlled / Argo CD projects, the branch a step's Git resource points at is resolved at release creation, before Octopus variables are evaluated — so it could not previously be set from GitHub Actions (variables resolve too late, defaulting the release to main). The server API, Go SDK, and CLI already support this via gitResources; only the Action lacked an input. This closes that gap.

Customer request SF-2251: deploy a feature branch to Dev from GitHub Actions by pointing the Update Argo CD Application Manifests step at the pushed branch.

How it flows

git_resources input → InputParameters.gitResources → CreateReleaseCommandV1.GitResources → POST /releases/create/v1. The step's SelectedGitResources on the created release then reflect the chosen ref.

Verification

Proven end-to-end against a real Octopus instance + a version-controlled Argo project: the built dist (run exactly as the runner invokes it) created a release whose SelectedGitResources targeted the feature branch's commit, and a real GitHub-hosted-runner workflow (push + pull_request) produced the same result.

Tests

Unit test asserting git_resources is parsed into gitResources (single and named-resource forms).

Landing (why this is a draft)

Requires GitResources on CreateReleaseCommandV1 from OctopusDeploy/api-client.ts#280. Once that merges and publishes:

1. Bump @octopusdeploy/api-client to the published version.
2. npm run build to regenerate dist/index.js.
3. Mark ready for review.

🤖 Generated with Claude Code