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

Design GlitchTip-to-Gitea issue filing workflow #74

New Issue
Open
opened 2026-07-02 05:43:46 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-02 05:43:46 -05:00
Owner
Copy Link
Copy Source

Design a workflow for filing Gitea issues from GlitchTip errors/events, including deduplication and linking.

This should remain design-only unless implementation is explicitly approved later.

Acceptance criteria

  • Defines what data goes into the Gitea issue title/body.
  • Defines labels such as source:glitchtip, bug, and status:triage.
  • Defines how to link back to GlitchTip.
  • Defines how to search for existing Gitea issues before creating a new one.
  • Defines deduplication key strategy using GlitchTip issue ID/fingerprint.
  • Defines redaction rules for stack traces, request data, cookies, headers, tokens, and PII.
  • Defines audit requirements for issue creation.
  • Defines confirmation/gating expectations before filing issues.
Design a workflow for filing Gitea issues from GlitchTip errors/events, including deduplication and linking. This should remain design-only unless implementation is explicitly approved later. ## Acceptance criteria * Defines what data goes into the Gitea issue title/body. * Defines labels such as `source:glitchtip`, `bug`, and `status:triage`. * Defines how to link back to GlitchTip. * Defines how to search for existing Gitea issues before creating a new one. * Defines deduplication key strategy using GlitchTip issue ID/fingerprint. * Defines redaction rules for stack traces, request data, cookies, headers, tokens, and PII. * Defines audit requirements for issue creation. * Defines confirmation/gating expectations before filing issues.
jcwalker3 added the giteadesignglitchtipworkflow labels 2026-07-02 05:44:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 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 design gitea glitchtip workflow
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#74
Delete Branch "%!s()"

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?