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
We should figure out how to test this work without spamming our GitHub releases. npm has dry-run, so perhaps GitHub has something similar?
Why
Currently creating a GitHub release is done locally on dev machines, including manually uploading a release artifact. Doing it via the GitHub API will hopefully mean a more controlled environment.
Who
Developers
Done when
We have a way of triggering this job (which could be manual, or could, for instance, check npm)
Have figured out how to generate and attach the release artifact automatically
Can create a GitHub release
We have updated the documentation for this step
The text was updated successfully, but these errors were encountered:
What
Automate the steps to create a GitHub release, including the creation of a release artifact, which currently (for some reason) happens in the publish to
npm
job.We should figure out how to test this work without spamming our GitHub releases.
npm
hasdry-run
, so perhaps GitHub has something similar?Why
Currently creating a GitHub release is done locally on dev machines, including manually uploading a release artifact. Doing it via the GitHub API will hopefully mean a more controlled environment.
Who
Developers
Done when
npm
)The text was updated successfully, but these errors were encountered: