-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
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
Post release to Discord in CI #3855
Post release to Discord in CI #3855
Conversation
data="{\"content\":\"https://github.com/typelevel/cats-effect/releases/tag/v$1\"}" | ||
data="{\"content\":\"https://github.com/typelevel/cats-effect/releases/tag/$1\"}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems easier to just pass the tag.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, the reason I didn't do it that way is because all the other scripts take a version number unprefixed by v
, and it's going to get very confusing if we make it inconsistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely easier here to just pass tag, but it's also inconsistent with the other scripts.
Presumably we eventually want to run the other scripts in CI too? We're just going to butt heads with this again. It's easier to pass a tag in GHA than it is to do string manipulation. Meanwhile, the scripts themselves can easily strip the |
That's fair. Can we change the other scripts then at the same time? This is exactly the sort of stuff that gets really confusing if we aren't strict about it. |
old_version="${1#v}" | ||
new_version="${2#v}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oooooh, fancy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fancy? I feel dirty 😩
Follow-up to #3711 that uses the configured secret.