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 Sep 20, 2024. It is now read-only.
Awesome suggestion @kamranayub! I would love to get this up and running.
A few questions:
Would you expect the "npm package" to be added to the comment like in the above screenshot? For instance if a mono-repo were to publish, would we need the package version of that publish to be reported back to the PR of each package published in that release?
Just wanted to show an existing approach that's supported natively in GitHub already, in case it helps in the interim until this feature is available.
If you go the commit URL for the merge commit on a PR, e.g., https://github.com/my-org/my-repo/commit/abc123, you can see all the tags in which it's included, which might correspond to a release:
Is your feature request related to a problem? Please describe.
It's common to ask, "What version was this issue or PR fixed in?"
Describe the solution you'd like
Semantic Release does this via the https://github.com/semantic-release/github plug-in
It adds a comment and labels issues and PRs that are included in the release.
Describe alternatives you've considered
n/a
Additional context
Here's what it looks like:
semantic-release/github#269
The text was updated successfully, but these errors were encountered: