-
Notifications
You must be signed in to change notification settings - Fork 8
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
baldrick pulls config from fork's master branch #111
Comments
Huh, it should be pulling from whatever GH gives us as the base branch: https://github.com/OpenAstronomy/baldrick/blob/master/baldrick/github/github_api.py#L781 |
Apparently base branch of the PR is the default branch of upstream |
I had a look at your PR, and I think it's fixing a symptom not the actual bug. According to everything I can find online, a Pull Request event is triggered from the upstream repo not the fork from which it originates. So all the GH API classes which get created in the event handling code should be pointing at upstream not the fork, and we should be using the base branch of the upstream as the place to pull the config. I think what we need to work out is why we are not alway getting the upstream when we create the repo object here: https://github.com/OpenAstronomy/baldrick/blob/master/baldrick/blueprints/github.py#L43 |
I also can't reproduce this bug on sunpy/Giles. I am wondering if you are seeing this on all astropy PRs or if something is wonky with just that one / user or something. |
Why would it have exception rules for a few users? Maybe we can do a |
So, this is the log after merging astropy/astropy#11483 . I still don't understand it. Seems to grab config twice, once from fork and once from upstream. And whatever happened didn't kick off the towncrier check. I think this event was tied to astropy/astropy#11456
|
And this is the log after I asked PR author to rebase and push, and still nothing on the PR check statuses (statii?).
|
The above log, combined with what I saw in astropy/astropy#11481
suggests that
baldrick
is attempting to read the config from a fork'smaster
, notupstream
.This would explain why it stopped running for my PRs because I deleted my fork's
master
branch a long time ago, as suggested in https://docs.astropy.org/en/latest/development/workflow/development_workflow.html#deleting-your-master-branch .And I clearly remember that the bot used to work despite my fork not having a
master
branch before but I don't remember when it stopped working. I just know it's been that way (broken) for quite some time; just didn't know why until now.The text was updated successfully, but these errors were encountered: