-
Notifications
You must be signed in to change notification settings - Fork 187
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
enable setting defaulBranch for pipeline repo creation #1959
enable setting defaulBranch for pipeline repo creation #1959
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #1959 +/- ##
=======================================
Coverage 61.10% 61.10%
=======================================
Files 37 37
Lines 4677 4677
=======================================
Hits 2858 2858
Misses 1819 1819 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
I wonder why the pipeline creation CI fails 🤷 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Suggested a couple of changes.
Additionally, I think it would be great if you could edit test_create.py
to check the default branch is set correctly
Lines 31 to 35 in dec66ab
def test_pipeline_creation(self): | |
assert self.pipeline.template_params["name"] == self.pipeline_name | |
assert self.pipeline.template_params["description"] == self.pipeline_description | |
assert self.pipeline.template_params["author"] == self.pipeline_author | |
assert self.pipeline.template_params["version"] == self.pipeline_version |
Ready for re-review. |
Looks great! You did not address adapting the tests in |
Thank you for the flowers. Forgot the note about the test. Added one. |
There's maybe still an issue with the default branch not being included in the template. I am not familiar enough with the templates and would like some input from someone who is about wether the default branch should be part of the template or not. |
For reference: https://nfcore.slack.com/archives/CE5LG7WMB/p1665850093986309
When a local
.gitconfig
specified theinit.defaultBranch
to anything else thanmaster
one sync test would fail.To make the tests system config agnostic, it is necessary to have a different way of telling nf-core tools what it should use as a default branch when creating new pipeline repositories. This PR implements just that in the internals and uses the feature to make tests pass on systems with
init.defaultBranch
not set tomaster
. It does not expose this feature to the CLI - this should maybe be the topic of another PR that then also updates the docs.PR checklist
CHANGELOG.md
is updateddocs
is updated