@@ -130,11 +130,11 @@ failed jobs of the picked tag, or of the newest tag before a pick, with the ones
130130when the range was cut at ` RELEASE_SCOPE_MAX_COMMITS ` , and how many rows have no tag yet, with a ` + ` when the cut
131131range holds no tag, so more untagged rows may lie below it. The failed jobs are those of the tag's pipeline and of
132132the main pipeline of its commit; failures in other rows show only when the line is opened.
133- Opening a line shows the service's environments, warnings, a link to create the next tag on the head when rows have no
134- tag yet, merge requests that are not merged yet, and its rows with
135- tags and their pipelines, merge requests or commits, Jira keys with their status, environments with the time each
136- first ran the row, and failed jobs; rows
137- out of scope are dimmed. Links, including the GitLab settings pages that warnings and errors point to, open in a new
133+ Opening a line shows the service's environments with when each was deployed , warnings, a link to create the next tag
134+ on the head when rows have no tag yet, merge requests that are not merged yet, and its rows with tags and their
135+ pipelines, merge requests or commits with when they were merged or committed , Jira keys with their status,
136+ environments with the time each first ran the row, and failed jobs; rows out of scope are dimmed.
137+ Links, including the GitLab settings pages that warnings and errors point to, open in a new
138138tab. Each tag has a ** pick** button: picking it highlights the rows it ships and closes the line again. A ` --jira `
139139report starts with each service's release tag picked. Services with neither a production deployment nor rows are left
140140out of the page.
0 commit comments