Jan Bronicki

Just linking a CNCF tracking issue: https://github.com/flatcar/Flatcar/issues/1877

If the `CODEOWNERS` file is static, maybe with each commit to the main branch, we could have a job that makes sure that the people present in `MAINTAINERS.md` are also...

Hi @tormath1 please take a look at this PR and let me know if this is what you would like to have 😄 https://github.com/flatcar/flatcar-template-project/pull/1

I fully agree that its important to let people have the ability of seeing that something is happening in other projects in which they do not "specialize". But I also...

Hi @flatcar/flatcar-maintainers @flatcar/nebraska-maintainers @flatcar/flatcar-contributors I hope you're all doing well. We have an ongoing discussion about setting up a `CODEOWNERS` file to streamline the review process for pull requests across...

Every PR has been merged and every repository now has a CODEOWNERS file! https://github.com/flatcar/Flatcar/issues/1791 - Following the resolution of this issue I think we can close this one as well...

List of repos without main branch protection: - [ ] https://github.com/flatcar/ue-rs - [ ] https://github.com/flatcar/flatcar-cloud-image-uploader - [ ] https://github.com/flatcar/flatcar-terraform - [ ] https://github.com/flatcar/container-linux-config-transpiler - [ ] https://github.com/flatcar/locksmith - [ ]...

> Thanks, this all looks good to me. Question: can we set this from the template repo? To avoid thinking about this when creating new repos? > > I just...

> Pt. 2, IMO, I’m happy with the current system as it helps preserve history — provided the PR commits are properly arranged. Additionally, it makes reverts easier. We should...

> > Pt. 2, IMO, I’m happy with the current system as it helps preserve history — provided the PR commits are properly arranged. Additionally, it makes reverts easier. We...