-
Notifications
You must be signed in to change notification settings - Fork 14
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
Enable default repo settings similar to other siderolabs repos #14
Comments
Yes, I'm all in for uniform repository settings :) I'll make sure we rework the repo-content with kres as soon as we have released 0.5.0. |
Yup great 👍 |
I'll put up a draft PR to help things to be easier, and once 0.5.0 is released, will enforce the repository settings. |
Oh, i didn't realize 0.5.0 is already cut that was fast, I'll start by renaming the branch to main, WDYT? |
I just now created the release :) Yes, if you will, please go. |
Done, might need this local updates: git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a |
Thanks. I've updated the workflow definition to reflect the branch rename, even though I suspect kres will make that obsolete anyway. |
Yeh, kres generates even gh workflow files |
Just adds in the golangcilint file from kres so this should be a no-op PR. Part of: siderolabs#14 Signed-off-by: Noel Georgi <[email protected]>
Just adds in the golangcilint file from kres so this should be a no-op PR. Part of: #14 Signed-off-by: Noel Georgi <[email protected]>
Enable kres and update repo branch settings. Fixes: siderolabs#14 Signed-off-by: Noel Georgi <[email protected]>
Enable kres and update repo branch settings. Fixes: siderolabs#14 Signed-off-by: Noel Georgi <[email protected]>
Coming in from this: #12 (comment)
i would be beneficial to have this repo have default settings similar to other repos under the organization.
Have a default main branch and have the standard repo branch protection settings enabled.
@robinelfrink / @lennardk I can help get this started
The text was updated successfully, but these errors were encountered: