Repository navigation
Name services by repo and group what picks leave behind by task - #56
Merged
Merged
Conversation
This was referenced Oct 24, 2026
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.
Services are named by their repository, such as
apifororg/team/api. Before, the page only cut off the prefix that every service shared, so services in different subgroups kept long paths. When two projects on the page share a name, such asshop/adminandlegacy/admin, each keeps as many parent groups as it takes to tell them apart. Projects that Jira issues link to but the report does not cover count too, since they appear on the page. Hovering over a name still shows the full path. The address, Tag pipelines, Compare, and Release post keep full paths because they get pasted elsewhere.Left behind by these picks is grouped by task. Each group opens with the task's Jira key, linked, and its summary. Below it come the services the task still misses, then each issue it depends on with its key, its summary, and the services that issue misses (or its status when it has no changes).
Each line gets an action where one exists:
needs Xhas a Pick X button, which picks the tag without opening the service.no tag yetlinks to create the next tag.not merged,merged into <branch>, andin prod or not mergedlink to the merge requests or commits.A Pick N needed tags button next to the title picks every needed tag at once, the newest per service. The mockup put this button on each task group. I moved it to the title because in the demo no group needs more than one tag, so a group button would repeat the line's own button.
The demo now links SHOP-38 to
partners/mobileinstead ofshop/mobile, and SHOP-44 also linkslegacy/admin. That way it shows a repo from another group and two projects with the same name.The report schema is unchanged, so this is a patch release.
Tests:
just test-ci(146 passed, 100% coverage),just test-smoke(25 passed),just lint. I also checked the demo in a browser.