wpengine / wpengine/hwptoolkit
ci: Release workflow creates a new PR each time
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 47
- Forks
- 3
- Avg merge
- 1m
- Merged PRs (30d)
- 19
Description
The release workflow currently has two issues:
- Creates a new PR for each trigger, instead of updating the existing one.
- Triggers on lock file changes, after each dependabot merge
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the release workflow and reviewing how it handles repeated triggers and lock file changes after Dependabot merges. Reproduce or trace both trigger paths, then confirm that repeated triggers update one PR and that lock file changes no longer create unwanted release PRs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 57/100