-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Rethink latest-tag-button
#6250
Comments
The feature also lets you:
I wonder if we can reduce it to:
This would let us split and reposition the feature. We don't need to show the latest version on every page. |
Here's my suggestion, I think it's a more direct solution to the original issue. The only missing part is that it requires 2 more clicks (without pageloads) to open "the same view, but in the latest tag." That's something I think is relatively rarely needed 🤔
|
Something to note:
This would also leave space for: |
Maybe we should just merge it with the branch/tag picker: On default branchTODO On non-default branchDo nothing, as mentioned:
On latest tagHomepageFile browserSame as above, the issue is where to put the compare button On non-latest tagHomepageHow to go to latest tag
So it's 1 click -> 3 clicks Unlike in file browser, it doesn't automatically open the tag tab, maybe we can automate that and save one click File browserHow to go to latest tag:
So it's 1 click -> 2 clicks, barely a difference |
I think we need to de-emphasize the importance/frequency of this action and the necessity to know the latest tag on every single page. I think This is why I suggest dropping
This is good enough for me, requires no features/changes from us. |
My proposal is about not losing any current info, of course cutting down them is welcome |
The new React-based views mentioned in #6152, no longer have enough space to show
latest-tag-button
Essentially the old view is only show on isRepoRoot
What do we do with this feature? It was initially added to:
Questions:
The text was updated successfully, but these errors were encountered: