Repository navigation
Conversation
The forge list at /tools renders a row only when the tool's pipeline state is 7 (published). That state is not a reliable record of whether a tool is live: on a production hub, 74 tools whose resource is published, whose access is public and which have a published tool version are still sitting at state 4 (installed) or 5 (updated), and so never appear. They span the whole history of the hub, from long-standing tools to ones added this year, so this is drift in the pipeline rather than a recent break. Keep the public list as it is -- ordinary visitors still see published tools only -- and let admins see the ones stalled at installed, updated or approved, so the gap is visible to the people who can act on it. Retired (8) and abandoned (9) stay hidden from everyone, as does anything the existing query already excludes. Every tool this restores for admins is one the query already returned, so each has a /opt/trac/tools directory and a working wiki link. Tools with no forge directory are still excluded, correctly: the rows link to the tool's Trac wiki, and there would be none to link to. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The forge list at /tools renders a row only when the tool's pipeline state is 7 (published). That state is not a reliable record of whether a tool is live: on a production hub, 74 tools whose resource is published, whose access is public and which have a published tool version are still sitting at state 4 (installed) or 5 (updated), and so never appear. They span the whole history of the hub, from long-standing tools to ones added this year, so this is drift in the pipeline rather than a recent break.
Keep the public list as it is -- ordinary visitors still see published tools only -- and let admins see the ones stalled at installed, updated or approved, so the gap is visible to the people who can act on it. Retired (8) and abandoned (9) stay hidden from everyone, as does anything the existing query already excludes.
Every tool this restores for admins is one the query already returned, so each has a /opt/trac/tools directory and a working wiki link. Tools with no forge directory are still excluded, correctly: the rows link to the tool's Trac wiki, and there would be none to link to.
Before you submit this pull request, please make sure:
Thanks!