Member-only story
3 Great Tips How I Improved Collaboration On Azure DevOps YAML Pipeline Templates
My experience with writing YAML pipeline templates for multiple teams made one thing clear to me:
Collaboration on shared resources can be a real challenge sometimes.
The biggest challenge is primarily that everybody has their own set of rules or approaches on how to develop YAML templates. And of course, that is not meant in a negative sense.
It’s good that everybody has different rules and/or approaches, as it supports creativity and innovation, especially in the early phase of a project that just started and want to make use of YAML templates.
Despite that fact, when you develop YAML templates for multiple teams and have a large contribution factor in your codebase, it can become difficult to determine what rules to follow.
You can look at the structure of the repository itself, and make a CONTRIBUTING.md where rules can be found, or you might be that pull request warrior that has sharp eyes, but still, people might contribute in a different way than you might have foreseen.
Is there then a way to set up rules or possibly a standard? Is it possible to enforce this standard when people contribute (and don’t bother the hell out of them)?
