-
Notifications
You must be signed in to change notification settings - Fork 9
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
bot autoupdating downstream to new url #39
Comments
I may be wrong, but my understanding was that this would be done by people (maybe scripted) but not using a GitHub Actions workflow.
@martinfleis can you please link all the projects you want updated here that fit the current definitons of "core" (#30 (comment))? |
My understanding was that a bot can do this and that @bsipocz knows how to deploy that bot.
Probably not by GHA. I am not sure. I may be raising the question in the wrong repo...
It is not about core packages, it is about the TEST WITH NIGHTLY WHEELS part of the SPEC 4. A lot of non-core downstream packages were already testing against nightly wheels uploaded to |
Okay great.
Okay. A thing to note is that the example given in SPEC 4 leaves people open to possible security issues (that should get fixed) and the pattern given in upload-nightly-action/README.md Lines 65 to 70 in ae43952
(i.e. the index is |
I'm going to close this as I think all users are now on the correct URL, but please comment if this isn't the case for anyone. |
While discussing the change of the home for nightlies, @bsipocz mentioned that once all core packages are uploading to a new location, there is a way to automatically open PRs downstream, changing the url from the old scipy one to the new scientific-python.
@bsipocz was there an attempt to do that? I haven't noticed it in any of the packages I'm involved with. Given the scipy repository is now outdated, it would be good to roll this out. I understood that all the necessary pieces were ready.
The text was updated successfully, but these errors were encountered: