Prompt for Forgejo token during release publishing
This commit is contained in:
parent
1bea5547a6
commit
e9d76cc4a2
3 changed files with 41 additions and 1 deletions
|
|
@ -76,6 +76,16 @@ Remove-Item Env:FORGEJO_PAT
|
|||
git pull --ff-only
|
||||
```
|
||||
|
||||
For an interactive, double-clickable option, run:
|
||||
|
||||
```text
|
||||
scripts\Publish-DeckyRelease.cmd
|
||||
```
|
||||
|
||||
It bypasses PowerShell's script policy only for the publisher process, prompts
|
||||
for the version and a hidden personal access token, and leaves the window open
|
||||
so any error can be read. The token is not saved.
|
||||
|
||||
The publisher creates the `v0.3.0` Forgejo release/tag at `main`, uploads the
|
||||
installer, signature, and metadata, then commits the tracked
|
||||
`releases/latest.json` through the Forgejo API. The final pull synchronizes that
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue