.github: make auto release #3259
Open
Conversation
This file contains 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
|
little problem, missing this for auto updated in vita3k |
Build number is provided in release title. |
|
auto updated get broken with this code |
|
The action I am trying to use does not seem to support the changes of the release notes(and I don't think the current one is user friendly). 🙃 |
|
is not possible adding description like current ? 🤔 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Vita3K can run more games and regressions are not unusual for now, it is better to retain past builds.
Looking at PCSX2, there does not appear to be a capacity limit on releases.
Release looks like this.
If you do not want a large number of releases created, i can change code to have a release created when a tag is created.