public/obsidian-livesync
1
0
Fork 0
mirror of https://github.com/vrtmrz/obsidian-livesync.git synced 2026-07-08 05:45:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

limit permission

Browse Source
This commit is contained in:
vorotamoroz
2026-07-08 03:24:33 +00:00
parent b8a4c824e2
commit 3efc72bab9
3 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/finalise-release.yml
+1
View File
@@ -15,6 +15,7 @@ on:
jobs: jobs:
finalise: finalise:
runs-on: ubuntu-latest runs-on: ubuntu-latest
environment: release
permissions: permissions:
contents: write contents: write
steps: steps:
.github/workflows/release.yml
+1
View File
@@ -25,6 +25,7 @@ on:
jobs: jobs:
build: build:
runs-on: ubuntu-latest runs-on: ubuntu-latest
environment: release
permissions: permissions:
contents: write contents: write
id-token: write id-token: write
devs.md
+1
View File
@@ -264,6 +264,7 @@ In short, the situation remains unchanged for me, but it means you all become a
## Release Workflow ## Release Workflow
This workflow is for maintainers. Contributors should update `## Unreleased` for user-facing feature or fix PRs, but do not need to run the release workflows. This workflow is for maintainers. Contributors should update `## Unreleased` for user-facing feature or fix PRs, but do not need to run the release workflows.
The `Finalise Release Tags` and `Release Obsidian Plugin` workflows use the `release` GitHub Environment. Configure Environment protection in the repository settings so tag creation and release publication require maintainer approval.
- Run the `Prepare Release PR` workflow with the target version. It creates the release branch, updates versions, moves the `## Unreleased` notes to the target version, commits the release preparation, pushes the branch, and opens a draft release PR. - Run the `Prepare Release PR` workflow with the target version. It creates the release branch, updates versions, moves the `## Unreleased` notes to the target version, commits the release preparation, pushes the branch, and opens a draft release PR.
- Do not tag the release branch when the PR is first created. Polish the release PR first, especially `updates.md`. - Do not tag the release branch when the PR is first created. Polish the release PR first, especially `updates.md`.