Reviewer, assignee, milestone, and project parity inputs #3

New issue

Closed

opened 2026-06-16 17:54:53 +00:00 by stephen · 0 comments

stephen commented

2026-06-16 17:54:53 +00:00

Owner

Why

The v1 action supports labels only. Common automation workflows need reviewers, assignees, milestones, or project linkage when opening/updating PRs.

Verified

action.yml has labels but no reviewers, assignees, milestones, or projects inputs.
No existing create-pull-request-action issues are filed.
Forgejo API supports enough of this surface to add incrementally.

Build

Add inputs and API calls where Forgejo supports them.
Make unsupported host versions warn clearly rather than fail unpredictably.
Add mock Forgejo tests for each supported field.

## Why The v1 action supports labels only. Common automation workflows need reviewers, assignees, milestones, or project linkage when opening/updating PRs. ## Verified - `action.yml` has labels but no reviewers, assignees, milestones, or projects inputs. - No existing create-pull-request-action issues are filed. - Forgejo API supports enough of this surface to add incrementally. ## Build - Add inputs and API calls where Forgejo supports them. - Make unsupported host versions warn clearly rather than fail unpredictably. - Add mock Forgejo tests for each supported field.

stephen added the

opportunity

labels

2026-06-16 17:54:53 +00:00

stephen referenced this issue from a commit

2026-06-17 01:48:21 +00:00

Add reviewer, assignee, milestone, and project inputs (#3)

stephen referenced this issue from a pull request that will close it,

2026-06-17 01:48:35 +00:00

Add reviewer, assignee, milestone, and project inputs #5

stephen closed this issue

2026-06-17 01:50:32 +00:00