How to create a new GEMU repository via KDE template
Kyndryl Developer Experience (KDE) provides a governed and automated workflow for creating GitHub Enterprise Managed Users (GEMU) repositories. This process ensures compliance with Secure SDLC (S-SDLC) standards, enforces organizational naming conventions, and integrates automated checks and approval mechanisms. Follow the steps mentioned below to create a new GEMU repository using the KDE template.
wrwrgwrgwrgwrg
Step 1: Access the KDE template
- Navigate to KDE Portal >Templates
- Select Repo Creation Template.
- Available templates include
- To create an empty default repository
- To create a repository with boiler plate code for a specific technology
- Each template comes with:
- Boilerplate code
- Pre-configured CI/CD pipelines
- Embedded S-SDLC checks (branch protection, PR review enforcement).
Step 2: Enter required information
Provide the following details to create your repository. Some fields are auto-populated based on your profile.
- Virtual Organization (Mandatory)
- Team Name (Optional)
- Repository Name (Mandatory)
- Example:
- bdg-sw-devx-kde-test (CTO organization)
- ac-project1-testrepo (Delivery organization)
- Justification
- State reason
Virtual Org naming convention
- Enforced format: org-team-project
- Supported Virtual Orgs:
- CTO
- Delivery
- Purpose:
- Ensures traceability
- Prevents naming conflicts
- Supports compliance and audit requirements
Step 3: Approval workflow
When you create a repository, an automated approval process starts.
- Level 1: Your manager reviews and approves the request.
- You can view approval status and audit logs in KDE for traceability.
Step 4: Automated checks and governance
The template provides automated checks to help ensure security, compliance, and consistency across all repositories. These checks include:
- Branch protection rules
- Mandatory PR reviews
- Restrictions on force pushes
- Integrated Security Scans:
- Mend.io for dependency checks
- Image scanning for container security
- Pre-commit validation for compliance.
Step 5: Post-creation actions
After the repository is created:
- The repository is auto-registered in KDE as a software entity for visibility and governance.
- Audit logs are maintained for all actions.
- Access requests within CTO or cross-org are managed via KDE through a multi-stage approval process.
Key benefits
Using the KDE template for GEMU repository creation offers the following advantages:
- Standardization: Ensure consistent naming and structure across all GEMU repos.
- Security: Provides built-in S-SDLC controls and automated compliance checks.
- Efficiency: Uses pre-approved templates to reduce setup time and minimize errors.
- Traceability: Maintains a complete audit trail and governance visibility in KDE.
FAQs
- Q: Are other Github operations changing due to repo creation via KDE? Ans: No, just the repository creation and repo access go through KDE. Other things are not changing and your Git access will not be revoked.
- Q: How to bring modifications to the templates ? Ans: The KDE framework is extensible through custom templates that can be shared.
- Q: Is there an API for repository creation ? Ans: Currently not avaliable. KDE API will be available shortly.
- Q: Can Virtual Org owners and approvers be changed. Ans: Yes, process is outlined by the SSDLC team
- Q: What happens if a GitHub rate limit is reached during repository creation—will the process fail gracefully, or could it result in a partially configured repository ? Ans: Any error, the flow fails cleanly without any partial set up.
- Q: Is there any dashboard or place to see all repos created through KDE? Ans: Repos created via KDE are automatically registered as entities which can be viewed in Software Entities page
- Q: If someone creates a repo by mistake, is there an easy way to delete or roll it back in KDE ? Ans: KDE does not support repo deletion. Needs to be done directly in Git