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

Design GlitchTip/Gitea deduplication and linking #78

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

Design deduplication and linking for GlitchTip-to-Gitea issue filing to prevent duplicate issue spam.

Focused split from #74 (GlitchTip-to-Gitea issue filing workflow), which references a dedup key strategy as a single criterion. This issue owns dedup/linking in full.

Acceptance criteria

  • Stores GlitchTip issue ID in the Gitea issue body or structured marker.
  • Stores GlitchTip fingerprint when available.
  • Searches existing open and closed Gitea issues before creating a new one.
  • Re-filing the same GlitchTip issue does not create a duplicate.
  • Existing issue receives a comment/link/update instead.
  • Applies source:glitchtip label.
  • Handles repeated/concurrent events safely.
  • Defines tests for deduplication behavior.
Design deduplication and linking for GlitchTip-to-Gitea issue filing to prevent duplicate issue spam. Focused split from #74 (GlitchTip-to-Gitea issue filing workflow), which references a dedup key strategy as a single criterion. This issue owns dedup/linking in full. ## Acceptance criteria * Stores GlitchTip issue ID in the Gitea issue body or structured marker. * Stores GlitchTip fingerprint when available. * Searches existing open and closed Gitea issues before creating a new one. * Re-filing the same GlitchTip issue does not create a duplicate. * Existing issue receives a comment/link/update instead. * Applies `source:glitchtip` label. * Handles repeated/concurrent events safely. * Defines tests for deduplication behavior.
jcwalker3 added the giteareliabilitydesignglitchtipworkflow labels 2026-07-02 05:46:56 -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 reliability 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#78
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?