mirror of
https://github.com/prdlk/leetcode.git
synced 2026-11-02 13:12:44 +00:00
ci(ci): update Close Topics workflow to handle Review issues and clarify descriptions
This commit is contained in:
1 parent
b2dffa4615
commit
1d77c5a8b5
2 files changed
+17
-9
No files matched your search
@@ -66,9 +66,12 @@ jobs:
|
||||
# tagged at the instant the last core problem closed. It reads the same rule
|
||||
# close-topics uses (apps/cli/topics.ts) straight off the sub-issues, so the
|
||||
# push that finishes a topic releases it in this run — no waiting for Close
|
||||
# Topics, which chains after this workflow. Reconciling: a run releases
|
||||
# every finished topic still missing one, so a manual dispatch backfills and
|
||||
# a problem closed by hand in the UI is picked up by the next run.
|
||||
# Topics, which chains after this workflow. A problem re-parented into a
|
||||
# `Review <N> — <Phase>` issue still belongs to its topic (recovered from
|
||||
# its parent_issue_removed event), so moving it never rewrites a release.
|
||||
# Reconciling: a run releases every finished topic still missing one, so a
|
||||
# manual dispatch backfills and a problem closed by hand in the UI is picked
|
||||
# up by the next run. Closing a finished Review issue is Close Topics' job.
|
||||
release:
|
||||
needs: close
|
||||
# Like close-topics: a partially failed close still closed some issues,
|
||||
|
||||
Reference in new issue
Block a user