fix: route releases through Forgejo PRs #151

Merged
barrettruth merged 1 commit from ci/release-pr-flow into main 2026-05-02 22:55:05 +00:00
Owner

Problem

The release script still tries to push directly to protected main and tag the pre-merge commit, which does not match the current Forgejo PR flow.

Solution

Make just release VERSION create a release/v* branch and Forgejo PR, and add just release VERSION --tag as the post-merge tag step that triggers the release workflow.

## Problem The release script still tries to push directly to protected `main` and tag the pre-merge commit, which does not match the current Forgejo PR flow. ## Solution Make `just release VERSION` create a `release/v*` branch and Forgejo PR, and add `just release VERSION --tag` as the post-merge tag step that triggers the release workflow.
fix: route releases through Forgejo PRs
All checks were successful
quality / Format (pull_request) Successful in 14s
quality / Test (pull_request) Successful in 39s
quality / Lint (pull_request) Successful in 1m5s
a173d35e56
barrettruth deleted branch ci/release-pr-flow 2026-05-02 22:55:05 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/vimdoc-language-server!151
No description provided.