-
Notifications
You must be signed in to change notification settings - Fork 56
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
DONT MERGE Master+ipynb #414
Conversation
Wait, the push should be done automatically for each push on master, right? Or what is this PR for? |
We don't push the ipynb's back to Master. This was just a lazy way to test the GHA activation. I tried to move forward with #320 but using conda in the action spins forever: https://github.com/OpenMS/pyopenms-docs/actions/runs/6719647447/job/18261670898?pr=320 |
9b1b43a
to
d19d8e5
Compare
I think we should use (micro)mamba instead of conda these days. Might help with runtime. |
ah ok came to say same thing... we don't usually push back the notebooks into master (to keep it clean). |
Something I did realize is that the way we do it now means past version of
the notebooks get wiped every time master+ipynb gets updated.
…On Thu, Nov 2, 2023 at 9:39 AM Timo Sachsenberg ***@***.***> wrote:
ah ok came to say same thing... we don't usually push back the notebooks
into master (to keep it clean).
—
Reply to this email directly, view it on GitHub
<#414 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABD3C6VXSAFWNL2S44NFDDYCNL4DAVCNFSM6AAAAAA6ZL6O7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJQGI4TCOJZGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yep. That's mainly why this branch should never be touched manually 😅 |
d19d8e5
to
98322d5
Compare
05ff659
to
07bb49d
Compare
07bb49d
to
61fd013
Compare
61fd013
to
b4c88e0
Compare
No description provided.