Unless @Rick-Methot-NOAA, has a different preference, I think it would be fine to just add the link to the ss3-windows-latest artifact from the build-ss3 workflow (e.g. ss3-windows-latest) since almost all of the pull requests in this repo are from folks on the SS3 team who are using Windows.
Describe alternatives you have considered
Continue navigating manually to the artifact within the actions page.
Statistical validity, if applicable
No response
Describe if this is needed for a management application
Describe the solution you would like.
As discussed in https://github.com/nmfs-ost/ss3-doc/issues/222, automatically adding a link to the compiled executable to a PR discussion would make it easier to access those files.
Unless @Rick-Methot-NOAA, has a different preference, I think it would be fine to just add the link to the
ss3-windows-latestartifact from the build-ss3 workflow (e.g. ss3-windows-latest) since almost all of the pull requests in this repo are from folks on the SS3 team who are using Windows.Describe alternatives you have considered
Continue navigating manually to the artifact within the actions page.
Statistical validity, if applicable
No response
Describe if this is needed for a management application
No response
Additional context
No response