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

Unable to create a PR from https://qchateau.github.io/conan-center-bot/#/updatable #111

Open
EstebanDugueperoux2 opened this issue Jul 20, 2023 · 11 comments

Comments

@EstebanDugueperoux2
Copy link

Hi,

I'm unable to create a PR from https://qchateau.github.io/conan-center-bot/#/updatable.
Trying to create a PR for libde265 I get a "Pull request creation failed. Validation failed: must be a collaborator" error message.
See also comments from conan-io/conan-center-index#18603 (comment).

Regards.

@jtbandes
Copy link
Contributor

I'm hitting the same error trying to create a PR for mcap: https://github.com/conan-io/conan-center-index/compare/conan-io:master...qchateau:ccb-mcap-1.2.0?expand=1

@jtbandes
Copy link
Contributor

FWIW, cc @ericLemanissier - I get the same error when trying to use your fork as well. https://github.com/conan-io/conan-center-index/compare/conan-io:master...ericLemanissier:ccb-mcap-1.2.0?expand=1
image

@ericLemanissier
Copy link
Contributor

OK. It must be that either CCI or github policy is refusing pull requests if the submitter is not contributor to the source repository.

@qchateau
Copy link
Owner

Yes it still works for me. I tried to change a few settings, can you retry from mine ?
Else, try to fork my fork (...) and open your PR from there

@ericLemanissier
Copy link
Contributor

Same error. Maybe it's because of Allowing edits by maintainers which is ticked by default?

@jtbandes
Copy link
Contributor

I still get the same error too. It seems like it could be a GitHub policy. Would it make sense to enable the bot itself to submit a PR (perhaps only upon request)?

@qchateau
Copy link
Owner

CCI owners did not want me to automatically open Para, and doing it "upon request" doesn't seem super easy to implement without additional infrastructure

@jtbandes
Copy link
Contributor

Do you think it's an issue with the upstream repo or with the fork? Maybe we should reach out to GitHub support to understand what the error really means by "must be a collaborator"?

@ericLemanissier
Copy link
Contributor

This should be raised to github support yes. It happens when the person submitting the PR is not a collaborator to the fork being pulled, so the issue could originate in both the fork or the upstream.

@jtbandes
Copy link
Contributor

I've opened a discussion here: https://github.com/orgs/community/discussions/61472

@Dobiasd
Copy link

Dobiasd commented Dec 27, 2023

And updates on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants