Applying GitOps principles to your operations
Could we use our Git repository as the source of truth for operational tasks, and somehow reconcile changes with our real-world view?
Could we use our Git repository as the source of truth for operational tasks, and somehow reconcile changes with our real-world view?
Consider the typical software development practices in an organization. Projects are commonly closed, and causes friction across engineering teams. But open source communities work asynchronously, openly, remotely and at global-scale. What if our internal teams could reuse those same practices?
Go beyond knowing GitHub as the home of open source and explore how GitHub Enterprise can help you transform your software engineering organization and practices.
With innersource, it’s important to measure both the amount of innersource activity and the quality of the code being created. Here’s how.
The innersource contribution percentage is the rate of contributions from people outside the team that originally authored the software. Let’s dive into what it can look like for your organization.
DRY your Actions configuration with reusable workflows (and more!)
Imagine you’re in an organization with over 2,000 repositories across several different product lines. It can be daunting task to find the right project.
Learn about five more reasons why every enterprise should make innersource a priority in 2020.
Build what’s next on GitHub, the place for anyone from anywhere to build anything.
Get tickets to the 10th anniversary of our global developer event on AI, DevEx, and security.