Skip to content
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

Closed
wants to merge 1 commit into from
Closed

DONT MERGE Master+ipynb #414

wants to merge 1 commit into from

Conversation

poshul
Copy link
Collaborator

@poshul poshul commented Nov 1, 2023

No description provided.

@poshul poshul marked this pull request as draft November 1, 2023 14:28
@jpfeuffer
Copy link
Contributor

Wait, the push should be done automatically for each push on master, right? Or what is this PR for?
Not that it's the best solution, but be careful if you change master+ipynb

@poshul
Copy link
Collaborator Author

poshul commented Nov 1, 2023

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

@github-actions github-actions bot force-pushed the master+ipynb branch 2 times, most recently from 9b1b43a to d19d8e5 Compare November 1, 2023 15:16
@jpfeuffer
Copy link
Contributor

I think we should use (micro)mamba instead of conda these days. Might help with runtime.

@timosachsenberg
Copy link
Contributor

ah ok came to say same thing... we don't usually push back the notebooks into master (to keep it clean).

@timosachsenberg timosachsenberg changed the title Master+ipynb DONT MERGE Master+ipynb Nov 2, 2023
@poshul
Copy link
Collaborator Author

poshul commented Nov 2, 2023 via email

@jpfeuffer
Copy link
Contributor

Yep. That's mainly why this branch should never be touched manually 😅

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.

4 participants