mirror of
https://github.com/UglyToad/PdfPig.git
synced 2026-03-10 00:23:29 +08:00
b9aa53166d
since actions do not have permissions to push directly to master and bot accounts to achieve the same are hard to manage we will change the release flow to work as follows. 1. manually invoke `prepare_release_pr.yml` action, this creates a new branch with the version of all project files updated and creates a pull request for that version. this pr then should be merged using rebase merge 2. `tag_release.yml` checks if the newest commit name starts with the text "Release " and also verifies if it changed the version of the package csproj. if both those conditions are met it will create and push a new tag, e.g. `v0.1.17` to master 3. `publish_nuget.yml` listens for new `v*` tags on master and triggers the nuget deployment this is all chat gpt code so who knows if it will work
40 lines
1020 B
YAML
40 lines
1020 B
YAML
name: Create Release PR
|
|
|
|
on:
|
|
workflow_dispatch
|
|
|
|
permissions:
|
|
contents: write
|
|
pull-requests: write
|
|
|
|
jobs:
|
|
bump_version:
|
|
runs-on: windows-2022
|
|
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
with:
|
|
fetch-depth: 0
|
|
|
|
- name: Calculate next version
|
|
id: version
|
|
run: |
|
|
$newVer = .\tools\get-next-main-version.ps1
|
|
echo "NEW_VERSION=$newVer" >> $env:GITHUB_ENV
|
|
.\tools\set-version.ps1 $newVer -UpdateAssemblyAndFileVersion
|
|
|
|
git config user.name "github-actions"
|
|
git config user.email "github-actions@github.com"
|
|
|
|
git checkout -b release/$newVer
|
|
git commit -am "Release $newVer"
|
|
|
|
- name: Create Pull Request
|
|
uses: peter-evans/create-pull-request@v6
|
|
with:
|
|
branch: release/${{ env.NEW_VERSION }}
|
|
base: master
|
|
title: "Release ${{ env.NEW_VERSION }}"
|
|
body: "Automated release PR."
|
|
delete-branch: true
|
|
merge-method: rebase |