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
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
When trying to link releases to output checking issues, I've noticed it is quite common to split a release into multiple releases (example here. This makes it a bit harder to track; ideally there would be a single release for each review.
I think this is because (though definitely worth confirming), if you have a release using multiple output patterns:
Fixing a typo becomes annoying
It is more challenging, when confirming the files to be released, to check you are only releasing what you want.
I think a way around this would be to make osrelease stepwise, where you enter a single file/pattern, press enter, confirm files to be released by that pattern and then confirm whether you would like to release more files. Repeat as necessary.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When trying to link releases to output checking issues, I've noticed it is quite common to split a release into multiple releases (example here. This makes it a bit harder to track; ideally there would be a single release for each review.
I think this is because (though definitely worth confirming), if you have a release using multiple output patterns:
I think a way around this would be to make osrelease stepwise, where you enter a single file/pattern, press enter, confirm files to be released by that pattern and then confirm whether you would like to release more files. Repeat as necessary.
The text was updated successfully, but these errors were encountered: