Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(action): atomic-branch/create-pr - Create/update PR with attestation

Open
#29 2 comments 0 reactions 1 assignee View on GitHub

@aRustyDev is already working on this.

Since Jan 27, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement new-action

Parent Epic

Part of #22 (Atomic Release Pipeline Actions)

Priority

P1 - Core W2 functionality

Description

Create a composite action that creates or updates a PR with attestation lineage.

For each artifact branch, creates a PR to the target branch that carries forward the attestation chain from the source PR.

Inputs

Input Required Default Description
artifact Yes - Artifact name
branch Yes - Source branch for PR
target-branch No main Target branch for PR
source-pr No - Source PR number (for lineage)
attestation-map No {} Attestation map to carry forward
source-branch No integration Original source branch name
token No github.token GitHub token

Outputs

Output Description
pr-number PR number (new or existing)
pr-action Action taken: "created", "updated", or "unchanged"
pr-url Full PR URL

Usage Example

- uses: arustydev/gha/actions/atomic-branch/create-pr@v1
  id: pr
  with:
    artifact: my-chart
    branch: charts/my-chart
    target-branch: main
    source-pr: 123
    attestation-map: '{"lint": "att-123"}'

- run: echo "PR: ${{ steps.pr.outputs.pr-url }}"

Source Reference

gha/.github/workflows/atomic-release-atomize-changes.yml:

  • Create/update PR step (lines 315-402)

Implementation Notes

  • Check for existing PR before creating
  • Include attestation map in PR body
  • Handle race conditions gracefully
  • Use conventional commit format for PR title
Dominant language
Shell
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aRustyDev/gh

All issues in aRustyDev/gh

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.