Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update safety and boundary docs for Jenkins/GlitchTip (#79) #89

Merged
sysadmin merged 1 commits from docs/issue-79-safety-boundary-updates into master 2026-07-02 14:21:50 -05:00
Conversation 0 Commits 1 Files Changed 3
+11 -2
sysadmin commented 2026-07-02 13:34:48 -05:00
Owner
Copy Link
Copy Source

docs: update safety and boundary docs for Jenkins/GlitchTip (#79)

Implements #79 by applying the ADR-0001 decisions to the existing documentation files:

  • Added glitchtip-mcp to tool boundaries and credential isolation.
  • Explicitly documented read-only-first policy and mutation gating.
  • Explicitly deferred Jenkins build triggers.
  • Clarified GlitchTip->Gitea filing as a gated, orchestrated workflow.

Closes #79.

docs: update safety and boundary docs for Jenkins/GlitchTip (#79) Implements #79 by applying the ADR-0001 decisions to the existing documentation files: * Added `glitchtip-mcp` to tool boundaries and credential isolation. * Explicitly documented read-only-first policy and mutation gating. * Explicitly deferred Jenkins build triggers. * Clarified GlitchTip->Gitea filing as a gated, orchestrated workflow. Closes #79.
sysadmin added 1 commit 2026-07-02 13:34:48 -05:00
docs: update safety and boundary docs for Jenkins/GlitchTip (#79) df840855cf
sysadmin merged commit 0a61e8a92d into master 2026-07-02 14:21:50 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#89
Delete Branch "docs/issue-79-safety-boundary-updates"

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?