GRI-581: the same repository boundary here, and the two duplicated process documents named #3
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage!3
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/GRI-581-repo-boundary"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The product owner, on GRI-581: "This way of thinking
counts for all repo's." So this repository gets the same treatment as
grimoire-of-helpdesk.What is here
A
.repo-boundarymanifest — what this repository holds, the patterns that donot belong in it and where each one goes instead — and a CI job that runs
repo-boundaryfromagent-toolsagainst it on every pull request. Exit 2,the check could not be made, fails the job: a boundary that was not checked
must not read like one that is clean (GRI-143).
Nothing is moved out. The check passes on this repository as it stands.
What the check found, and did not move
Two documents here are copies of documents in
grimoire-of-helpdesk, and bothhave drifted:
grimoire-of-helpdeskplan/process/agent-git-identity.mdplan/process/branching-and-release.mdThree homes for two documents, none of them in step. That is the same defect as
the two block generators of GRI-654, at document scale: nothing in either copy
can see the other, and an agent that reads the short one is reading rules that
are 764 lines behind.
They are named as
[[allow]]exceptions on GRI-715rather than deleted here. Deleting a document an agent is instructed to read,
before the single replacement in
agent-toolsis in place, breaks the reader.GRI-715 moves them once and repoints everybody.
agent-toolspull request #97 adds the rule and the checker; this needs itmerged first, because the CI job fetches
bin/repo-boundaryfromdevthere.