-
Notifications
You must be signed in to change notification settings - Fork 0
First pass at a reusable PR creation workflow. #74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
env: | ||
PR_HEAD_BRANCH: ${{ inputs.head-branch }} | ||
PR_BASE_BRANCH: ${{ inputs.base-branch }} | ||
run: git checkout -b "$PR_HEAD_BRANCH" "origin/$PR_BASE_BRANCH" |
Check failure
Code scanning / octoscan
Use of "git checkout" in a bash script with a potentially dangerous reference. Error
- name: Save patch file as an artifact | ||
uses: actions/upload-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0 | ||
with: | ||
name: pr-artifacts-${{ github.run_id }}-patch | ||
path: release-diff.patch |
Check failure
Code scanning / zizmor
commit with no history in referenced repository Error
- name: Save commit message as an artifact | ||
uses: actions/upload-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0 | ||
with: | ||
name: pr-artifacts-${{ github.run_id }}-commit-message | ||
path: commit-message.md |
Check failure
Code scanning / zizmor
commit with no history in referenced repository Error
- name: Save pull request body as an artifact | ||
uses: actions/upload-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0 | ||
with: | ||
name: pr-artifacts-${{ github.run_id }}-pr-body | ||
path: pr-body.md |
Check failure
Code scanning / zizmor
commit with no history in referenced repository Error
DO NOT MERGE. PROOF OF CONCEPT
Proposed changes
This is for exploring how a generic PR creation workflow could be created for reuse across workflows.
The other main problem this hopes to address is that commits and PRs authored by GitHub Action workflows do not have the required capabilities to trigger the corresponding GitHub Actions workflows.
This would be used in combination with something like newfold-labs/wp-plugin-bluehost#419, which allows each repository to control which workflows create pull requests.
Type of Change
Production
Development
Visual
Checklist
Further comments