AZ-400: Designing and Implementing Microsoft DevOps Solutions

Branching Strategies for Source Code

Embracing Inner Source with Forking Workflow

In this article, we explore how adopting an InnerSource approach with a forking workflow can significantly enhance collaboration across your organization. By incorporating open-source development principles internally, your team can drive innovation and efficiency.

Insight

Adopting a forking workflow empowers every contributor to actively participate in the project, fostering transparency and collective problem-solving.

Empowering Every Contributor

A fork-based pull request system ensures that every team member has the opportunity to propose changes. This inclusive approach invites diverse ideas and solutions from across the organization, much like inviting everyone to the table. It not only democratizes development but also promotes ownership and accountability within teams.

Integrating Open Source Practices Internally

InnerSource leverages the proven methods of open-source development right within your company. By integrating these practices, teams collaborate more transparently and efficiently, fostering a secure environment for innovation. This method helps in building a culture where continuous feedback and improvements are seamlessly incorporated into ongoing projects.

Accommodating Varied Levels of Contribution

In large organizations with multiple teams and varying levels of expertise, the forking workflow stands out as an ideal solution. It enables both frequent contributors and occasional participants to make meaningful contributions without overwhelming the core project. This balanced approach harnesses the collective expertise of the team while ensuring streamlined project management.

Implementing the Forking Workflow

The following steps outline how to implement a forking workflow within your organization:

  1. Fork the main repository to your personal workspace.
  2. Create a new branch for your feature or bug fix.
  3. Commit your changes and push them to your fork.
  4. Open a pull request against the main repository.
  5. Engage in peer review and collaborate on required changes.

For a clear understanding of the entire workflow process, review the detailed descriptions provided above to develop a comprehensive mental model of this approach.

Important

Ensure that team members are familiar with internal guidelines and best practices to maintain consistency and avoid conflicts during the contribution process.

Watch Video

Watch video content

Previous
Demystifying Git Hooks