| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Recently I have the same issue. |
Sorry, something went wrong.
|
@das-g Hi Raphael, can we do something about the required checks? Would like to merge this one. Thanks! |
Sorry, something went wrong.
I don't think I have the required access level to circumvent required checks. For that you'll probably have to ask the owners of the DjangoGirls GitHub organization. As for why no status was reported by the build, I have no idea. Maybe @ekohl has some insight into that? https://github.com/DjangoGirls/tutorial/pull/1859/checks says "Workflow runs completed with no jobs", which isn't what I'd expect from our CI setup. |
Sorry, something went wrong.
|
In my experience, that's just what GitHub sometimes does. There are sometimes outages and it's best to force the checks to restart. I prefer to rebase the PR, but you can also close/open the PR. Given this was opened from someone's master branch I don't feel comfortable force pushing for @Anemaygi. |
Sorry, something went wrong.
|
Closing to be able to re-open to force a rebuild. |
Sorry, something went wrong.
|
Reopening to force a rebuild. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Changes in this pull request:
Solves one of the problems from #1858