chore: move closed issue specs from open/ to closed/ folder#1935
Merged
josecelano merged 1 commit intoJun 23, 2026
Merged
Conversation
- Move SI-30 (torrust#1924) and SI-31 (torrust#1925) specs to docs/issues/closed/ - Update spec-path frontmatter in both files - Update EPIC.md links to point to closed/ paths - Mark EPIC.md quick list checkboxes as done for both issues - Update SI-33 references to point to ../closed/ path for SI-30
There was a problem hiding this comment.
Pull request overview
Moves completed issue spec files SI-30 (#1924) and SI-31 (#1925) from docs/issues/open/ to docs/issues/closed/, and updates cross-references in EPIC/SI-33 docs to point to the new locations.
Changes:
- Updated SI-33 doc links/references to SI-30’s new
closed/path. - Updated EPIC #1669 links and checklist/table status entries for SI-30 and SI-31.
- Updated
spec-pathfrontmatter in the moved closed issue specs.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/issues/open/1930-1669-si-33-rest-api-contract-first-architecture.md | Updates references/links to SI-30 to point to the closed spec location. |
| docs/issues/open/1669-overhaul-packages/EPIC.md | Updates EPIC links and checklist/table entries for SI-30 and SI-31 to closed locations / DONE status. |
| docs/issues/closed/1925-1669-si-31-configure-cargo-deny-for-layer-boundary-enforcement.md | Updates spec-path after moving the spec to closed/. |
| docs/issues/closed/1924-1669-si-30-decouple-rest-api-core-from-udp-internals.md | Updates spec-path after moving the spec to closed/. |
Comments suppressed due to low confidence (2)
docs/issues/closed/1924-1669-si-30-decouple-rest-api-core-from-udp-internals.md:8
- Frontmatter for a closed issue spec should use
status: doneper the documented frontmatter guidance (seedocs/issues/closed/1810-add-frontmatter-to-docs-markdown-files.md). Also, issue specs should usedoc-type: issue(notspec).
docs/issues/closed/1925-1669-si-31-configure-cargo-deny-for-layer-boundary-enforcement.md:7 - Frontmatter for a closed issue spec should use
status: doneper the documented frontmatter guidance (seedocs/issues/closed/1810-add-frontmatter-to-docs-markdown-files.md).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Member
Author
|
ACK 663035a |
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.
Moves the spec files for completed subissues SI-30 (#1924) and SI-31 (#1925) from
docs/issues/open/todocs/issues/closed/.spec-pathfrontmatter in both moved filesPre-merge checks:
cargo machete --with-metadata— passcargo deny check bans— passlinter all— passcargo test --doc --workspace— pass