-
Notifications
You must be signed in to change notification settings - Fork 58
add building of test documentation of RTD #169
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
Conversation
48eb673
to
55a444a
Compare
0943d35
to
82d9b64
Compare
931290c
to
81afebb
Compare
867d27e
to
eb15f46
Compare
eb15f46
to
a545197
Compare
This seems to work, @akhmerov, what do you think? |
a545197
to
86dd87d
Compare
First of all, this is at best a temporary solution because of the following reasons:
But even with that in mind, I still don't understand whether this satisfactory. My main question is: what will happen if a user that isn't a team member opens a PR? I can imagine several different possible outcomes:
In order to come to a decision on this PR I would like to know for sure which of these options is realized. Is there a document that describes the permissions model of azure pipelines with forks? |
7a62147
to
e613544
Compare
42f0b67
to
995835a
Compare
91e38f1
to
bc190a7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @akhmerov that to merge this we would need to:
- know what happens when someone opens a PR from their fork of adaptive
- allow multiple PRs to be open at the same time without each clobbering the other's docs deployment
- somehow hide all these "test" builds in readthedocs so that it's not confusing for users.
995835a
to
3b935bc
Compare
@akhmerov and @jbweston, I've opened #262 with a different account to see what happens. As I expected, no other person will be able to force push to our repo. Therefore, building the docs will only work for the core maintainers, and since nearly all of the PRs that have ever been made come from us, I believe that that's fine. I don't think your other point trump the fact that right now we do not have any tests. Right now, the docs are also broken and it's terrible to debug. I say, let's merge this as it is! |
It seems that since the initial implementation, rtd has enabled documentation building for PRs: https://blog.readthedocs.com/building-docs-for-pull-requests/, @basnijholt what do you think? |
181b9fd
to
20d4c7f
Compare
@akhmerov, I've requested the feature and we've got it! See for example https://adaptive--263.org.readthedocs.build/en/263/ |
This builds the documentation for each branch on https://adaptive.readthedocs.io/en/test_documentation
Todo: