-
Notifications
You must be signed in to change notification settings - Fork 155
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
Impossible to create new repositories with teams in version > 2.1.X #547
Comments
@svg153 You are running this in |
Possibly because I added this code for error handling and it is incorrectly reporting 404. Probably, better to ignore the 404 since the repo itself doesn't exist at this point. |
@svg153 I tested the 2.1.1-rc.2 (which has a fix to ignore 404 in dry-run) and it seems to work. I was able to test a config for a new repo with teams. However, I have to test it further. Let me know if that works as expected. |
TL;DRTested with safe-setting running with Correct, the validator no longer fails and leaves a message in the PR and in the check. For me, this issue is closed. But I leave it to your choice. ImprovementsAlthough the message displayed is not very explicit. I think we could continue with the improvements to the reports that were included in 2.1.0 (great job). But it is true that the tool has improved a lot (since the first time I used the tool almost two years ago) Thanks. DescriptionIn this case, I would like to see everything that is going to be added. Because right now in that PR, you only see a PR comment from safe-setting with a table in with only the header, there are no rows. And in the check I only know that there is "Breakdown of changes" with a table with the name of the repo. I think this can cause a bit of confusion as you don't clearly see what you are going to do. It seems that the report has been left halfway, giving the feeling that something has been broken. ExpectedTo give a specific example of this demo organization, I would expect a summary of the final consolidated configuration (like one of the debug message in the run), between general (setting.yml), suborg and specific to the repo (repo.yml) ThanksI really appreciate the work you are doing on this tool. I hope that GitHub will, at some point, give the true support that this tool deserves. Thank you very much for responding so soon. All the best. |
I'm preparing a demo for next Tuesday, and I would like to use the latest version 2.1.X since it includes improvements in the status report and the dry-run.
But...
Problem Description
I basic organization (for my demo: https://github.com/svg153-org/admin/) with only one team, when you try to create a new repository creating a PR, the validator fails, stating that it cannot verify the team that already exists on GitHub for that repository because it doesn't exist.
NOTE: i configured
restrictedRepos
, take into account for the validatior reportsFails with > 2.1.0, see below.
Works with 2.0.25, see this -> https://github.com/svg153-org/admin/pull/5/checks
But even if you ignore it, it still doesn't create it.
What is actually happening
What is the expected behavior
The validator doesn't fail in the pull request when you create a new repository. After merging into the main branch, you can create the repository.
Error output, if available
The first part is when creating the repository, which fails.
The second part is when, in the same pull request, you remove the "teams" block from the settings.yml.
Go to the public pull request linked: svg153-org/admin#4
When I removed the team block from the safe-settings file
Context
Are you using the hosted instance of probot/settings or running your own?
Own
If running your own instance, are you using it with github.com or GitHub Enterprise?
github.com
Version of safe-settings
Failed con >2.1.1, But not with 2.0.25
Version of GitHub Enterprise
The text was updated successfully, but these errors were encountered: