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

docs: re-land release version SOP with v1.1.0 audit lessons (#111) #119

Open
jcwalker3 wants to merge 1 commits from docs/issue-111-release-version-sop into master
pull from: docs/issue-111-release-version-sop
merge into: Scaled-Tech-Consulting:master
Conversation 0 Commits 1 Files Changed 2
+192
jcwalker3 commented 2026-07-02 19:53:27 -05:00
Owner
Copy Link
Copy Source

Re-land the release version SOP documentation, updated with v1.1.0 audit lessons (PR closed but unmerged results in files missing from master, requiring post-merge validation of file/commit presence). Closes #111.

Re-land the release version SOP documentation, updated with v1.1.0 audit lessons (PR closed but unmerged results in files missing from master, requiring post-merge validation of file/commit presence). Closes #111.
jcwalker3 added 1 commit 2026-07-03 02:24:48 -05:00
docs: re-land release version SOP with v1.1.0 audit lessons (#111) 9d6a2e0a5f
jcwalker3 force-pushed docs/issue-111-release-version-sop from a6da65c82b to 9d6a2e0a5f 2026-07-03 02:24:48 -05:00 Compare
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin docs/issue-111-release-version-sop:docs/issue-111-release-version-sop
git checkout docs/issue-111-release-version-sop
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#119
Delete Branch "docs/issue-111-release-version-sop"

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?