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

Outdated list of branches in project settings #11313

Closed
donmccurdy opened this issue May 6, 2024 · 2 comments
Closed

Outdated list of branches in project settings #11313

donmccurdy opened this issue May 6, 2024 · 2 comments

Comments

@donmccurdy
Copy link

Details

Note that both projects use the same GitHub repository, in the two subfolders below:

https://github.com/visgl/deck.gl/tree/master/bindings

Expected Result

We hadn't updated our Read the Docs sites for a while, and our builds currently fail with errors. Those errors are presumably our own fault, and I'm working on fixing them and getting the sites republished. My intended workflow would be:

  1. Push changes to a branch, donmccurdy/pydeck-dev
  2. Build from branch, observe errors
  3. Fix errors, push to branch, repeat

Actual Result

In both projects Read the Docs currently shows an outdated list of git branches, not including any of the branches I've created since last Friday. Without that, I'd need to push these changes to master, and since this is a large shared repository, I'd much rather not do trial-and-error on the master branch.

Is there something I can do to force Read the Docs to refresh the branch list, or to start a build from a branch that isn't currently listed? Is this a bug, or user error? I don't think we have any web hooks enabled, we push builds manually. Thanks!

@donmccurdy
Copy link
Author

Go figure, the branch has just appeared in the list! 😅

I don't think I did anything to cause it to appear now, I just created this branch today, but I'd been looking for a previous branch since Friday... In any case, I am unblocked, but will keep this open in the hope of learning what might have happened.

@humitos
Copy link
Member

humitos commented May 28, 2024

I'm happy that this issue is solved. I think it was probably a network blip or a Celery task that wasn't triggered for some reason. Let us know if it happens to you again.

@humitos humitos closed this as completed May 28, 2024
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

2 participants