Create Repository Settings Keeper

[derberg]

Reason/Context

We have 60 repositories in AsyncAPI organization and it is impossible to stay in sync with settings across all repositories.

We have https://github.com/asyncapi/.github/blob/master/repository-settings.md but it is completely ignored, thus also no longer updated.

Description

We need an application that enables us to manage the settings of the GitHub repository through a config file stored in a given repository.

• Imagine you have a file in a repo that is called .projects.settings.keeper
• it is a yaml file with structure that has info about:
  • discussions: true - that enables discussions tab for project
  • pr: ['squashandmerge'] - that enables only squash and merge on PRs
  • there should be a list of branch protection settings and default workflows that should be blocking PRs
• there also are extra settings like sonarcloud: true or coveralls: true that means the application should make sure sonarcloud or coveralls are enabled for a given project
• basing on CODEOWNERS the app adds given users as maintainers of the repo
• once .projects.settings.keeper is created, global workflow synchronization is triggered to get default workflows into the repo

For GSoC participants

• you will write some JS code
• you will learn GitHub Actions and GitHub API
• you will play a lot with different REST APIs to integrate them together

[Abhinav0909]

Hey,This feature sounds interesting.I am new to open source and ci/cd.So could you guide me throughout the process of making it.I want to contribute to this feature.So can you assign it to me.

[Abhinav0909]

And forget to mention that I am participant of openforce 2022.

[derberg]

Hey, sorry for not getting back to you sooner, this issue was not on the list of openforce and I was not checking it too often, sorry. Are you still interested?

[Abhinav0909]

Ok yeah you can assign to me

[Abhinav0909]

But you can guide me throughout the process

[derberg]

I definitely can guide you. No need to assign, if is enough if you state in comment that you want to work on it.

this will be a totally new GitHub Action that will have to be created. Might be that there is already some application available that is doing it though. So as long as you understand requirements, I suggest first conducting detailed research on what solutions are available atm that maybe we could reuse.

Let me know if more explanation on requirements is needed

[derberg]

I remove it from GSoC for now, I think there are other more important issues to handle

[ritik307]

Hi, @derberg I would like to work on this. If possible can you kindly guide me on how I can start?😊