Skip to content

Conversation

@pcm32
Copy link
Member

@pcm32 pcm32 commented Feb 11, 2024

No description provided.

@pcm32
Copy link
Member Author

pcm32 commented Feb 13, 2025

@irisdianauy @anilthanki can we merge this? it is just documentation. If you OK it, I can do it.

4. Iterate with the CI on the branch until all test pass with the new changes and dependencies.
5. Get reviews and merge to develop.
6. Open a bump branch in bioconda, making sure that it points to the develop branch of this repo rather than the pypi release and that all dependencies in bioconda reflect what is currently in the test-env.yaml file of this repo (which was used to test in the feature branch here in points 2 to 4).
7. Once the tests passes in bioconda, ask the bot to fetch the artifacts, download the linux artifact (to run the tests against that artifact or inside the artifact container). Leave the bioconda branch in draft and do not merge it (and probably add a message saying so) until you can verify that the created artifact can be used to run the tests (see steps below).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so only merge if everything works till step 13, correct?

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