Skip to content

chore(issues): archive closed issue #1671 spec and update cleanup skill#1929

Merged
josecelano merged 3 commits into
torrust:developfrom
josecelano:chore/cleanup-completed-issues
Jun 21, 2026
Merged

chore(issues): archive closed issue #1671 spec and update cleanup skill#1929
josecelano merged 3 commits into
torrust:developfrom
josecelano:chore/cleanup-completed-issues

Conversation

@josecelano

Copy link
Copy Markdown
Member

Archives the spec for issue #1671 (IPv4/IPv6 client metrics) from docs/issues/open/ to docs/issues/closed/.

Changes

  • IPv4/IPv6 client metrics: support per-client IP family labels and separate socket bindings #1671 spec archived: Verified issue is CLOSED on GitHub, moved via git mv
  • Frontmatter updated: status: done, spec-path → closed path, last-updated-utc → today
  • Workflow checkboxes ticked: manual verification, acceptance criteria review, committer verification, spec moved
  • Progress log entry: archiving action documented
  • Skill updated: cleanup-completed-issues/SKILL.md v1.3 — clarified branch/PR workflow, removed premature stage-2 deletion logic, added mandatory branch creation step, added PR step

Verification

  • Pre-commit hooks passed (cargo machete, linter all, cargo test --doc --workspace)
  • Files moved with git mv

…closed

Move the spec for the IPv4/IPv6 client metrics feature from
docs/issues/open/ to docs/issues/closed/ after GitHub issue closure.

- Update ISSUE.md frontmatter: status: open → done, spec-path → closed path, last-updated-utc → today
- Mark workflow checkboxes as complete
- Add progress log entry for archival
- Add frontmatter to research-dual-stack-portability.md
…h and PR workflow

- Archive is the only automated stage; permanent deletion is user-driven

- Mandatory branch creation (never commit to develop)

- Added step to open a PR targeting develop

- Updated workflow checkboxes and progress log guidance

- Removed premature stage-2 deletion logic
Copilot AI review requested due to automatic review settings June 21, 2026 10:27
@josecelano josecelano requested a review from a team as a code owner June 21, 2026 10:27
@josecelano josecelano self-assigned this Jun 21, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Archives the closed issue #1671 specification into the docs/issues/closed/ buffer and updates the cleanup-completed-issues skill to reflect the current archiving workflow.

Changes:

  • Updated issue spec frontmatter/status and workflow checkpoints for closed state.
  • Added frontmatter to the #1671 research document in the closed spec folder.
  • Revised the cleanup skill to emphasize branch/PR workflow and remove deletion guidance.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
docs/issues/closed/1671-ipv4-ipv6-client-metrics/research-dual-stack-portability.md Adds frontmatter metadata to the archived research doc (needs semantic-links to match docs conventions).
docs/issues/closed/1671-ipv4-ipv6-client-metrics/ISSUE.md Marks the issue spec as done and updates spec-path/date + workflow/progress log for archiving.
.github/skills/dev/planning/cleanup-completed-issues/SKILL.md Updates the archiving workflow steps (branching, pre-commit, PR creation) but contains a couple of actionable instruction issues.
Comments suppressed due to low confidence (1)

docs/issues/closed/1671-ipv4-ipv6-client-metrics/research-dual-stack-portability.md:4

  • The new frontmatter block is missing the repo’s standard semantic-links section. Other non-issue Markdown docs under docs/ include semantic-links (even when they also have other metadata), and the frontmatter guidance in docs/issues/closed/1810-add-frontmatter-to-docs-markdown-files.md expects it for general docs. Add a minimal semantic-links section (at least linking back to the parent ISSUE).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +45 to +47
git checkout develop
git pull torrust develop
git checkout -b chore/cleanup-completed-issues
--repo torrust/torrust-tracker \
--base develop \
--head {your-fork-remote}:chore/cleanup-completed-issues \
--title "chore(issues): archive closed issue #{N} spec to docs/issues/closed" \
## Lifecycle

Closed issue specs are **not deleted immediately**. They go through a two-stage lifecycle:
Closed issue specs follow a single automated stage:
- Use UPSTREAM_REMOTE variable with --ff-only for pull
- Fix PR title template: #${N} instead of #{N}
- Clarify lifecycle wording per review suggestion
- Add semantic-links to research-dual-stack-portability.md
- Add supplementary doc frontmatter guidance to skill
@josecelano

Copy link
Copy Markdown
Member Author

ACK 0a07150

@josecelano josecelano merged commit 4dc6c6e into torrust:develop Jun 21, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants