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

feat: make Gitea MCP profile activation and runtime identity state explicit (#131) #132

Open
jcwalker3 wants to merge 1 commits from feat/issue-131-profile-identity-clarity into master
pull from: feat/issue-131-profile-identity-clarity
merge into: Scaled-Tech-Consulting:master
Conversation 0 Commits 1 Files Changed 4
+685 -11
jcwalker3 commented 2026-07-04 01:04:11 -05:00
Owner
Copy Link
Copy Source

Implements explicit visibility into the active profile, authenticated identity, and allowed/forbidden operations. Adds dynamic profile activation and switching tools, and documents the safety/switching rules. Resolves Issue #131.

Implements explicit visibility into the active profile, authenticated identity, and allowed/forbidden operations. Adds dynamic profile activation and switching tools, and documents the safety/switching rules. Resolves Issue #131.
jcwalker3 added 1 commit 2026-07-04 01:04:12 -05:00
feat: implement profile activation and runtime identity clarity (#131) a0e7d3360e
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 feat/issue-131-profile-identity-clarity:feat/issue-131-profile-identity-clarity
git checkout feat/issue-131-profile-identity-clarity
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#132
Delete Branch "feat/issue-131-profile-identity-clarity"

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?