Skip to content

[Build] Build and publish api doc#46

Merged
hughperkins merged 84 commits intomainfrom
hp/pdoc
Jul 7, 2025
Merged

[Build] Build and publish api doc#46
hughperkins merged 84 commits intomainfrom
hp/pdoc

Conversation

@hughperkins
Copy link
Collaborator

@hughperkins hughperkins commented Jun 25, 2025

Issue: #

Brief Summary

Doc for each branch is published to:

https://ideal-adventure-2n6lpyw.pages.github.io/[branch-name]/taichi.html

For example, this branch is hp/doc, so the docs are at:

Note taht this pr depends on hp/manylinux. branch, so probably best to approve/merge that PR first :)

copilot:summary

Walkthrough

copilot:walkthrough

@hughperkins
Copy link
Collaborator Author

hughperkins commented Jul 2, 2025

@duburcqa So without contents write, this fails:

Screenshot 2025-07-02 at 8 43 54 AM

https://github.com/genesis-company/taichi/actions/runs/16028004337/job/45224022646?pr=46

(PS I wish github would warn me, when I try to paste a comment, and screenshot didnt upload yet... 😓 )

@duburcqa
Copy link
Contributor

duburcqa commented Jul 2, 2025

Maybe it is because this is a private organization? Another weird behavior I don’t quite understand…

@hughperkins
Copy link
Collaborator Author

Maybe it is because this is a private organization? Another weird behavior I don’t quite understand…

URL for where you are using workflow_call, along with secrets in the child call? (My understanding is this is somehow related to their security model, rather than to public/private 🤔)

@hughperkins
Copy link
Collaborator Author

(happy to create a new public repo, in my personal github, and we can try different things there too, to compare)

@duburcqa
Copy link
Contributor

duburcqa commented Jul 2, 2025

Ok now I understand, I think many of the weird quirks we are seeing here seem to be related to using workflow_call, which makes your workflow "reusable". Did you do this on purpose? If so, could you explain me what it is supposed to do?

After checking the documentation very quickly, this at least explain the issue with explicitly specifying the secrets that are required. I guess it is the same for the write permission. For the weird URL, it is probably unrelated though.

@hughperkins
Copy link
Collaborator Author

Thanks!

@hughperkins hughperkins enabled auto-merge (squash) July 7, 2025 13:40
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

Successfully merging this pull request may close these issues.

3 participants