You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As explained by the title this will start automatically creating winget manifests for you when a new version is published on GitHub.
A few things are needed, so follow these steps or else the workflow will not run:
Go to your account settings from the top-right:
Bottom-left go to Developer Settings
Then go to Personal Access Tokens and then Tokens (classic):
Then click Generate new-token, and go on Generate new token (classic):
Here as Note put: Blink Winget Releaser, Expiration set it to No Expiration (If you want to create an expiration date go ahead, but this would mean repeating this process at the end of its lifetime), and scope select the following:
Then just scroll down and hit Generate token, after just copy the token and keep it handy
Then come back to this repository and click Settings:
Then go to Secrets and Variables and click on Actions:
Then click `New repository secret:
Name should be: WINGET_TOKEN and Secret should be the one you copied from before, then just click Add Secret
This is how the Winget maintainers prefer to do it by adding an Alpha to the Package Identifier. When releases become stable instead of alpha, these should then go into prayag17.Blink, instead of prayag17.Blink.Alpha, which means another workflow needs to be done for stable releases.
EDIT: I adjusted the workflow to include the stable too for whenever that is ready.
This is how the Winget maintainers prefer to do it by adding an Alpha to the Package Identifier. When releases become stable instead of alpha, these should then go into prayag17.Blink, instead of prayag17.Blink.Alpha, which means another workflow needs to be done for stable releases.
EDIT: I adjusted the workflow to include the stable too for whenever that is ready.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DO NOT POST SECRET HERE
As explained by the title this will start automatically creating winget manifests for you when a new version is published on GitHub.
A few things are needed, so follow these steps or else the workflow will not run:
Developer SettingsPersonal Access Tokensand thenTokens (classic):Generate new-token, and go onGenerate new token (classic):Blink Winget Releaser, Expiration set it toNo Expiration(If you want to create an expiration date go ahead, but this would mean repeating this process at the end of its lifetime), and scope select the following:Then just scroll down and hit
Generate token, after just copy the token and keep it handySettings:Secrets and Variablesand click onActions:Nameshould be:WINGET_TOKENandSecretshould be the one you copied from before, then just clickAdd Secret