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

docs: design glitchtip to gitea issue filing workflow (#74) #94

Merged
jcwalker3 merged 1 commits from docs/issue-74-glitchtip-filing-workflow into master 2026-07-02 14:57:54 -05:00
Conversation 1 Commits 1 Files Changed 1
+56
sysadmin commented 2026-07-02 14:48:24 -05:00
Owner
Copy Link
Copy Source

Implements #74 by outlining the architecture and safety boundaries for the orchestrated workflow that files Gitea issues from GlitchTip events.

Closes #74.

No secrets, tags, or release states were altered. Changes are purely documentation.

Implements #74 by outlining the architecture and safety boundaries for the orchestrated workflow that files Gitea issues from GlitchTip events. Closes #74. No secrets, tags, or release states were altered. Changes are purely documentation.
sysadmin added 1 commit 2026-07-02 14:48:25 -05:00
docs: design glitchtip to gitea issue filing workflow (#74) 31f5bf9975
jcwalker3 reviewed 2026-07-02 14:57:33 -05:00
jcwalker3 left a comment
Owner
Copy Link
Copy Source

Reviewed PR #94 as jcwalker3 / prgs-author-reviewer. Checks passed: changed-file guard, git diff --check, py_compile for mcp_server.py/manage_labels.py/gitea_auth.py, bash -n scripts/clear-provenance, pytest tests/ -q, and secret/provenance sweep. Manual review confirms the PR is documentation/design only, changes only docs/architecture/glitchtip-to-gitea-workflow-design.md, stays within #74, contains no implementation code, secrets, generated artifacts, release/tag changes, or credential material, keeps GlitchTip MCP read-only with Gitea issue filing in an orchestrator, requires preview/confirmation and Gitea profile/audit gates, uses redaction/allowlist expectations, and defers deduplication/linking to #78.

Reviewed PR #94 as jcwalker3 / prgs-author-reviewer. Checks passed: changed-file guard, git diff --check, py_compile for mcp_server.py/manage_labels.py/gitea_auth.py, bash -n scripts/clear-provenance, pytest tests/ -q, and secret/provenance sweep. Manual review confirms the PR is documentation/design only, changes only docs/architecture/glitchtip-to-gitea-workflow-design.md, stays within #74, contains no implementation code, secrets, generated artifacts, release/tag changes, or credential material, keeps GlitchTip MCP read-only with Gitea issue filing in an orchestrator, requires preview/confirmation and Gitea profile/audit gates, uses redaction/allowlist expectations, and defers deduplication/linking to #78.
jcwalker3 merged commit e730c391a2 into master 2026-07-02 14:57:54 -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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#94
Delete Branch "docs/issue-74-glitchtip-filing-workflow"

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?