Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Do not generate dco-merge-queue.yml for private repos #277

Open
daniel-zullo-frequenz opened this issue Jun 12, 2024 · 1 comment
Open

Do not generate dco-merge-queue.yml for private repos #277

daniel-zullo-frequenz opened this issue Jun 12, 2024 · 1 comment
Labels
part:ci Affects the GitHub workflow and other parts for running CI priority:low This should be addressed only if there is nothing else on the table type:enhancement New feature or enhancement visitble to users
Milestone
Untriaged

Comments

@daniel-zullo-frequenz
Copy link
Contributor

What's needed?

Merge queues might not be available for private repos where an enterprise plan is needed

Proposed solution

dco-merge-queue.yml should not be generated for private repos if merge queues are not available

Use cases

No response

Alternatives and workarounds

No response

Additional context

No response
@daniel-zullo-frequenz daniel-zullo-frequenz added part:❓ We need to figure out which part is affected priority:❓ We need to figure out how soon this should be addressed type:enhancement New feature or enhancement visitble to users priority:low This should be addressed only if there is nothing else on the table part:ci Affects the GitHub workflow and other parts for running CI and removed part:❓ We need to figure out which part is affected priority:❓ We need to figure out how soon this should be addressed labels Jun 12, 2024
@llucax
Copy link
Contributor

llucax commented Jun 12, 2024

I would like to add more options to how to generate the templates to enabled/disable features individually, like use_merge_queues or support_arm, then we could have a predefined set of defaults per type of repo (lib, actor, etc.) and repo visibility (private, public). But it is a dream, not sure if I will ever have enough time to do it :D

@llucax llucax added this to the Untriaged milestone Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
part:ci Affects the GitHub workflow and other parts for running CI priority:low This should be addressed only if there is nothing else on the table type:enhancement New feature or enhancement visitble to users
Projects
None yet
Milestone
Untriaged
Development

No branches or pull requests
2 participants
@llucax @daniel-zullo-frequenz