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

docs: add post-merge file-presence verification to merge workflow (#112) #118

Merged
sysadmin merged 1 commits from fix/issue-112-post-merge-file-presence into master 2026-07-02 19:41:56 -05:00
Conversation 1 Commits 1 Files Changed 3
+17 -9
jcwalker3 commented 2026-07-02 19:23:44 -05:00
Owner
Copy Link
Copy Source

Add explicit instructions to verify that expected files or commits are actually present on master before reporting a PR as merged. Update the merge-pr template, Gitea-Tools runbook, and portable skill documentation. Closes #112.

Add explicit instructions to verify that expected files or commits are actually present on master before reporting a PR as merged. Update the merge-pr template, Gitea-Tools runbook, and portable skill documentation. Closes #112.
jcwalker3 added 1 commit 2026-07-02 19:23:45 -05:00
docs: add post-merge file-presence verification to merge workflow (#112) 255cfc87dd
sysadmin reviewed 2026-07-02 19:41:53 -05:00
sysadmin left a comment
Owner
Copy Link
Copy Source

Approved after independent review. Scope is limited to #112 post-merge file-presence verification docs/templates; validation passed.

Approved after independent review. Scope is limited to #112 post-merge file-presence verification docs/templates; validation passed.
sysadmin merged commit fbf1bc5f5c into master 2026-07-02 19:41:56 -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#118
Delete Branch "fix/issue-112-post-merge-file-presence"

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?