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
closing-remarks
: options to exclude pre-release tags (feature request)
#7206
Comments
That's a misuse of tags that causes conflicts at every push/pull, see note in https://stackoverflow.com/a/19300065
|
We can't add options to Refined GitHub, see: |
I see, I understand that options are too much burden. But I respectfully disagree that UPDATE: Even if one uses a different, unique tag name for each nightly release; say nightly-20240101, |
The main issue is that this feature answers the question:
Pre-release is literally a release. If 1.0.1-beta includes the PR, should we said "This PR hasn't been released yet"? Because that sounds like a lie/wrong. I'd potentially classify nightly releases as releases, but maybe we can make an exception because you probably still want to release manually later. Perhaps we can:
|
People would be mostly looking for:
while some might be also interested whether the PR has appeared in any pre-release versions (e.g. snapshot versions or release candidates). Checking the tag name/pattern such as nightly or digits would work (#7208) but this might too specific given that you don't want to allow options; there might be many corner cases. However, in Github releases there is a very clear binary signal telling: Pre-release v.s. normal/stable/full release. (See #2239, #2905, Manage releases - item 10, and Releases REST API - So my proposal is: to show either the first non-pre-release, the first pre-release as a fallback (if there is no stable release out), or both. |
A couple of issues with that:
I don’t think I want to overcomplicate this with logic that may vary across repos. The feature answers that question alone and it can't afford to make guesses around which tag the user prefers to see. Considering that probably there isn't even an API for this (i.e. get the tags that contain this commit), we can't even begin to consider releases. |
Thanks for your help and support! Yes, I do see that this is blocked by a technical limitation that the current Github REST API lacks something like A side note is that, if this feature worked as you intended (as in #7208) then it should have shown "v0.9.0" instead of "nightly". So it's the same issue as #7208 -- |
Description
The feature
closing-remarks
would show in which tag the PR (commit) first appeared:However, when the project publishes
nightly
or some sort of preview (unreleased) tag, it will shownightly
as the first tag. This is usually not an informative information; instead, users would want to see the first "release" version, excluding all the pre-release tags.Suggestions
Example URLs
PR: https://togithub.com/neovim/neovim/pull/22060
Merged commit: https://togithub.com/neovim/neovim/commit/27b81af19c498892f4b0444ad29b7be842f8e7b8
Shows "This pull request first appeared in nightly"; should be "first appeared in v0.9.0." (the commit is included in v0.9.0, ..., v0.9.5, stable, and nightly).
The text was updated successfully, but these errors were encountered: