-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Repository Settings Keeper #137
Comments
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. |
And forget to mention that I am participant of openforce 2022. |
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? |
Ok yeah you can assign to me |
But you can guide me throughout the process |
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 |
I remove it from GSoC for now, I think there are other more important issues to handle |
Hi, @derberg I would like to work on this. If possible can you kindly guide me on how I can start?😊 |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Just as a suggestion, I would say we should investigate and evaluate the usage of Terraform and the GitHub provider. |
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.
.projects.settings.keeper
discussions: true
- that enables discussions tab for projectpr: ['squashandmerge']
- that enables only squash and merge on PRssonarcloud: true
orcoveralls: true
that means the application should make sure sonarcloud or coveralls are enabled for a given project.projects.settings.keeper
is created, global workflow synchronization is triggered to get default workflows into the repoFor GSoC participants
The text was updated successfully, but these errors were encountered: