We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If we wanted to be fancy, we could use release.yml as per https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes
release.yml
It would require me to stop committing directly to master and actually start using PRs.
There does not seem to be a better option other than copy pasting non-PR things though?
It would be nice to have a table of all the appimages with some info, so users aren't confused by having 50 files there.
As a side note, is there a point in keeping the zsync and zsync sha256 files in the assets?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
If we wanted to be fancy, we could use
release.yml
as per https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notesIt would require me to stop committing directly to master and actually start using PRs.
There does not seem to be a better option other than copy pasting non-PR things though?
It would be nice to have a table of all the appimages with some info, so users aren't confused by having 50 files there.
As a side note, is there a point in keeping the zsync and zsync sha256 files in the assets?
The text was updated successfully, but these errors were encountered: