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 healthchecker-release & runtime-ci-pools repos #749

Conversation

jrussett
Copy link
Contributor

Follow up to: #505

We ended up renaming these repos but never added them to org/cloudfoundry.yml

Also cloudfoundry/diego-ci-pools should be deleted (it's empty and will be empty).

Follow up to: cloudfoundry#505

We ended up renaming these repos but never added them to
org/cloudfoundry.yml

Also cloudfoundry/diego-ci-pools should be deleted (it's empty and will
be empty).
@beyhan
Copy link
Member

beyhan commented Jan 11, 2024

Usually, we let the org automation first create the new repo and then execute the renaming. @stephanme do you have experience how the org automation behaves in this situation.

@beyhan beyhan requested review from a team, rkoster, beyhan, stephanme, ameowlia and ChrisMcGowan and removed request for a team January 15, 2024 10:58
@beyhan beyhan added the toc label Jan 15, 2024
@stephanme
Copy link
Contributor

IIRC the org automation doesn't delete repos, creates missing repos and will update existing repos. It simply diffs the cloudfoundry.yml list with the github org content.

Don't forget to update the repos in the WG charter (yaml part). Otherwise access won't be granted to the teams.

@beyhan beyhan merged commit 48ccf67 into cloudfoundry:main Jan 16, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants