You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 235a271
Browse filesBrowse the repository at this point in the historyBrowse files
Mark fully deployed services, show picks as chips, and move Release into a folding side column (#27)
* Mark fully deployed services and move Release into a tabbed side column
* Mark services with a picked tag and clear the pick from the line
* Show the picked tag as a chip and fold the Release column while a service is open
Copy file name to clipboardExpand all lines: README.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,23 +129,27 @@ as one line: what production runs, the picked tag, how many merge requests or co
129
129
failed jobs of the picked tag, or of the newest tag before a pick, with the ones allowed to fail counted apart, a mark
130
130
when the range was cut at `RELEASE_SCOPE_MAX_COMMITS`, and how many rows have no tag yet, with a `+` when the cut
131
131
range holds no tag, so more untagged rows may lie below it. The failed jobs are those of the tag's pipeline and of
132
-
the main pipeline of its commit; failures in other rows show only when the line is opened.
132
+
the main pipeline of its commit; failures in other rows show only when the line is opened. A service whose
133
+
production runs the head of the default branch, with no rows left to ship, is marked green as fully deployed.
133
134
Opening a line shows the service's environments with when each was deployed, warnings, a link to create the next tag
134
135
on the head when rows have no tag yet, merge requests that are not merged yet, and its rows with tags and their
135
136
pipelines, merge requests or commits with when they were merged or committed, Jira keys with their status,
136
137
environments with the time each first ran the row, and failed jobs; rows out of scope are dimmed.
137
138
Links, including the GitLab settings pages that warnings and errors point to, open in a new
138
-
tab. Each tag has a **pick** button: picking it highlights the rows it ships and closes the line again. A `--jira`
139
-
report starts with each service's release tag picked. Services with neither a production deployment nor rows are left
139
+
tab. Each tag has a **pick** button: picking it highlights the rows it ships and closes the line again, which then
140
+
shows the picked tag as a blue chip. The chip's `×` clears the pick without opening the line. A `--jira` report starts
141
+
with each service's release tag picked. Services with neither a production deployment nor rows are left
140
142
out of the page.
141
143
142
144
The address keeps the picks after `#`, as `team/api=2.4.0&team/web=5.12.0`, so sharing or reloading the page keeps
143
145
them. An address with picks replaces the release tags of a `--jira` report; picks that are not in the report, such as
144
146
a tag that a later run no longer lists, are skipped with a warning. Clearing every pick empties the address, so a
145
147
reload starts from the release tags again.
146
148
147
-
**Release** at the bottom turns the picked tags into three lists and a release post, each with a copy button and a
148
-
text box to copy from by hand, since browsers allow the copy button only over HTTPS:
149
+
**Release**, in a column next to the services that stays in view while they scroll, or below them on a narrow screen,
150
+
turns the picked tags into three lists and a release post. While a service is open, the column folds into a strip
151
+
with the number of picked tags and tasks, so the rows get the full width; clicking the strip closes the service. Each has a tab of its own, with a copy button and a text box
152
+
to copy from by hand, since browsers allow the copy button only over HTTPS:
149
153
150
154
-**Jira tasks**: the keys of every in-scope row from each picked tag down to production, without duplicates, with
151
155
summary and a status badge: grey to do, blue in progress, green done. Copy them one per line or as a JQL
0 commit comments