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
Some of the things I'd like to add to each release:
Summary of what was built, potentially the plan.yml file contains
everything needed.
Arguments passed to both ./configure and make. This will require
changes in the build script.
Capture ./configure output and upload it as a release asset.
Add a code block to description with SHA256 sums for all attached assets.
Potentially generated by simply combining the content of each *.sha256
asset.
Upload the Emacs source tarball downloaded by the build script as a asset
on each release.
For now these should all be relatively easy to deal with as each release will
only have a single build for macOS 10.15 on x86_64. Once we get another OS or
architecture the process will need to be able to deal with two concurrent builds
attaching different assets and updating relevant parts of the description.
The text was updated successfully, but these errors were encountered:
jimeh
changed the title
Populate GitHub Release description with relevant info about the build
Improve GitHub Releases (description, extra assets)
May 11, 2021
Some of the things I'd like to add to each release:
plan.yml
file containseverything needed.
./configure
andmake
. This will requirechanges in the build script.
./configure
output and upload it as a release asset.Potentially generated by simply combining the content of each
*.sha256
asset.
on each release.
For now these should all be relatively easy to deal with as each release will
only have a single build for macOS 10.15 on x86_64. Once we get another OS or
architecture the process will need to be able to deal with two concurrent builds
attaching different assets and updating relevant parts of the description.
The text was updated successfully, but these errors were encountered: