-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Conditionally skipped builds are "pending" instead of "passed" #9791
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
Labels
Bug
A bug
Comments
We need to track the GitHub settings for "Required Builds" here. The PR referred here #9788 will make it impossible to use required builds together with skipped builds AFAICT. The skipped builds will turn out yellow and the PR will never be merge-able. |
I am debugging this now, and think I've found the issue. |
ericholscher
added a commit
that referenced
this issue
Dec 15, 2022
This was because we were using this logic to return a relative URL, and then sending it to GitHub: * https://github.com/readthedocs/readthedocs.org/blob/f86b5376ffc70242bdd677cb02f016429ff6bd4b/readthedocs/oauth/services/github.py#L459-L460 * https://github.com/readthedocs/readthedocs.org/blob/f86b5376ffc70242bdd677cb02f016429ff6bd4b/readthedocs/builds/models.py#L343-L349 Fixes #9791
humitos
added a commit
that referenced
this issue
Feb 2, 2023
* Fix status reporting on PRs with the magic exit code This was because we were using this logic to return a relative URL, and then sending it to GitHub: * https://github.com/readthedocs/readthedocs.org/blob/f86b5376ffc70242bdd677cb02f016429ff6bd4b/readthedocs/oauth/services/github.py#L459-L460 * https://github.com/readthedocs/readthedocs.org/blob/f86b5376ffc70242bdd677cb02f016429ff6bd4b/readthedocs/builds/models.py#L343-L349 Fixes #9791 * Fix link_to_build defaults * Fix tests * Comment on usage * Fix test * Use same logic as absolute_url * VCS commit status: send absolute URL to docs when built successfully - remove `link_to_build` since it's not required - base the decition on `Build.state` and `Build.success` --------- Co-authored-by: Manuel Kaufmann <[email protected]>
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PRs end up having the "pending" state although a build has been correctly and intentionally skipped.
Example:
#9789
https://readthedocs.org/projects/dev/builds/18859457/
In another PR, the build wasn't skipped even though it seems to have contained no changes:
#9734
The text was updated successfully, but these errors were encountered: