-
Notifications
You must be signed in to change notification settings - Fork 149
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
Fixing release check and test docs in concrete-python CI #1163
base: main
Are you sure you want to change the base?
Conversation
BourgerieQuentin
commented
Nov 27, 2024
eaabc46
to
0ccd780
Compare
aa7cffa
to
bfe4f81
Compare
bfe4f81
to
7ce764a
Compare
7f44bee
to
bd77f88
Compare
925573c
to
991af9d
Compare
…ifacts in case of failure
The The real question however is why does the docs generation delete the |
I tried locally but it's too much different then the CI. However, the configuration file is generated correctly |
I can see should be related to ml-tooling/lazydocs#72 |
f6ff79a
to
032f2a1
Compare
it was previously changing the file header which then affects the docs
the current self-hosted runner will have the repo initialized from previous jobs, which will sometimes lead to weird behavior