Repository navigation
Add private GitHub team mode within the CRM skill - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Teams can now share a private GitHub workspace while continuing to use the installed CRM skill in their respective AI systems. Agents prepare isolated drafts, bind confirmation to an exact preview/base, submit protected proposals and verify the published receipt. There is no separate CRM application or server.
The runtime includes stable GitHub member identities, scoped record mutations, immutable reader snapshots, stale-base handling, retry recovery, owned cleanup and a pinned data-integrity workflow. Trusted validation rebuilds browser views instead of trusting submitted HTML. Frozen exports without CRM data also exclude team membership and operation receipts. README, skill routing, installable package and the German/English landing page describe the setup and visual team flow.
Validation: actual native CRM helpers and bare Git repositories exercise setup, parallel proposals, stale previews, failed pushes, lost merge responses, readers, exports, forged identities, derived labels, tampered views and erasure identities. GitHub HTTP/policy is simulated in these tests; no live customer workspace was configured. The product regression workflow runs all suites and checks package reproducibility.
Beta boundary: repository writers must be trusted to preserve the workflow and checks. Skill roles are not independent GitHub access roles and do not isolate hostile workflow authors. All repository readers can copy the shared data/history; current-record erasure does not purge Git history.