Skip to main content
Bringing open-source collaboration into your enterprise accelerates innovation while maintaining internal control. In this guide, we’ll explore how to implement an InnerSource strategy using a fork-and-pull workflow.

​
1. Empower Every Contributor

A fork-based pull request model democratizes code contributions. Whether you’re a core maintainer or a first-time contributor, the process is the same:
  1. Fork the main repository: 
    gh repo fork your-org/awesome-project --clone=true
  2. Create a feature branch in your fork: 
    git checkout -b feature/your-improvement
  3. Implement your changes and commit: 
    git add .
git commit -m "Describe your change"
  4. Open a pull request against the upstream repository: 
    gh pr create --base main --head your-username:feature/your-improvement
This inclusive workflow ensures everyone—from designers to QA engineers—can propose enhancements, boosting visibility and idea diversity.

​
2. Apply Open Source Practices Internally

Mirror familiar OSS patterns to build trust and streamline approvals without exposing proprietary code:
  • Code Reviews: Peer review enforces quality and shared ownership.
  • Version Control: Leverage Git branching strategies to track features and hotfixes.
  • Continuous Integration: Automate builds and tests on every pull request.
Maintain strict access controls and branch protection rules to keep your internal codebase secure.

​
3. Scale for Large Teams

A fork-driven model naturally accommodates different engagement levels. Teams and contributors can specialize without stepping on each other’s toes:
RoleResponsibilitiesBest Practices
Core MaintainersDefine roadmap, review PRs, enforce standardsProtected branches, release checklists
Regular ContributorsDeliver new features, address review feedbackIssue templates, CI/CD pipelines
Occasional ContributorsSubmit minor fixes, update docsPR templates, clear contribution guides
By assigning clear roles and leveraging pull-request approvals, you maintain governance while tapping into collective expertise.
Next, we’ll dive into the step-by-step implementation of the fork workflow, including CI integration and automation.

Watch Video