-
Notifications
You must be signed in to change notification settings - Fork 110
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
Harmonize usage of --dry-run vs --dryrun in create-sibling-gitlab #6013
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6013 +/- ##
===========================================
- Coverage 90.16% 65.05% -25.12%
===========================================
Files 315 312 -3
Lines 42196 42165 -31
===========================================
- Hits 38047 27429 -10618
- Misses 4149 14736 +10587
Continue to review full report at Codecov.
|
+1 on harmonizing into |
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.
Makes sense! Thx!
It would be good to discontinue the use of dryrun
in the tests, though.
PR datalad#5949 deprecated the parameter --dryrun in favor of --dry-run in create-sibling{github,gogs,gitea,gin}. This change fixes datalad#6011 by adding this deprecation and parameter alternative to create-sibling-gitlab as well, in order to harmonize the usage of this parameter across the family of create-sibling-* commands. TST: Discontinue use of deprecated dryrun in tests
Right, thanks much for catching this. I have replaced them, and force-pushed. |
The Appveyor failure is a network glitch, I think
|
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.
Thanks for the update!
This adds a
--dry-run
parameter tocreate-sibling-gitlab
to match the corresponding parameter increate-sibling-{github,gin,gogs,gitea}
, and deprecates the current--dryrun
option.The PR also includes a small doc fix to the URL pointing to the documentation of python gitlab