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.

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

Add repo/CI access for codeowners from STACKIT #97

Closed
Tracked by #96
timebertt opened this issue Mar 27, 2024 · 7 comments
Closed
Tracked by #96

Add repo/CI access for codeowners from STACKIT #97

timebertt opened this issue Mar 27, 2024 · 7 comments
Assignees
Labels
area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related area/os Operation system related kind/enhancement Enhancement, improvement, extension status/closed Issue is closed (either delivered or triaged)

Comments

@timebertt
Copy link
Member

timebertt commented Mar 27, 2024

How to categorize this issue?

/area os open-source
/kind enhancement

What would you like to be added:

As part of #96, @dergeberl and @timebertt are added as codeowners of this repository.

To the Gardener CI/CD team:
Can you ensure to grant us the following permissions, please?

  • maintain permissions in this repository
  • permission to trigger release pipelines for this repository

Why is this needed:

This will allow us to merge PRs, add other maintainers, and solve problems like this and this.

@gardener-robot gardener-robot added area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related area/os Operation system related kind/enhancement Enhancement, improvement, extension labels Mar 27, 2024
@oliver-goetz
Copy link
Member

@NiclasMoldenhauer please check Tim's request.
STACKIT is the main user of coreos extension, so it would make perfect sense, if they are able to maintain it too.

@NiclasMoldenhauer
Copy link

NiclasMoldenhauer commented Mar 28, 2024

Approved from management side 👍
@zkdev Please proceed.

@zkdev
Copy link
Member

zkdev commented Mar 28, 2024

@timebertt @dergeberl

permission to trigger release pipelines for this repository

You should have received an invitation for a GitHub Team in the meantime.
Once accepted, you should be able to trigger Concourse pipelines (you will have to re-auth in Concourse UI if you are logged-in already).
Could you please confirm that pipeline access is working as expected, e.g. by triggering an head-update job?


maintain permissions in this repository

Repository local Write role was assigned to you.
Administrative access to repositories is currently not available for external contributors.


add other maintainers

Please request access for new maintainers via repository local GitHub issue (as with this issue).

@timebertt
Copy link
Member Author

Thanks a lot, sounds good to me!

Could you please confirm that pipeline access is working as expected, e.g. by triggering an head-update job?

Works!

@zkdev zkdev removed their assignment Mar 28, 2024
@dergeberl
Copy link
Collaborator

Thanks,

Could you please confirm that pipeline access is working as expected, e.g. by triggering an head-update job?

Works also for me 🎉

@zkdev zkdev assigned timebertt and unassigned NiclasMoldenhauer Apr 2, 2024
@zkdev
Copy link
Member

zkdev commented Apr 2, 2024

@timebertt can we close this? :-)

@timebertt
Copy link
Member Author

Yes, thanks!
/close

@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/open-source Open Source (community, enablement, contributions, conferences, CNCF, etc.) related area/os Operation system related kind/enhancement Enhancement, improvement, extension status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

No branches or pull requests

6 participants