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

cmd ref: document new subcommand remote rename #1301

Closed
karajan1001 opened this issue May 17, 2020 · 7 comments · Fixed by #1318 or #1283
Closed

cmd ref: document new subcommand remote rename #1301

karajan1001 opened this issue May 17, 2020 · 7 comments · Fixed by #1318 or #1283
Labels
A: docs Area: user documentation (gatsby-theme-iterative) C: ref Content of /doc/*-reference type: enhancement Something is not clear, small updates, improvement suggestions

Comments

@karajan1001
Copy link
Contributor

karajan1001 commented May 17, 2020

Related to issue iterative/dvc#3599.

@jorgeorpinel jorgeorpinel added A: docs Area: user documentation (gatsby-theme-iterative) type: enhancement Something is not clear, small updates, improvement suggestions labels May 17, 2020
@PseudoNerd

This comment has been minimized.

@jorgeorpinel

This comment has been minimized.

@jorgeorpinel jorgeorpinel changed the title Add new command dvc remote rename cmd ref: document new subcommand remote rename May 18, 2020
@karajan1001
Copy link
Contributor Author

karajan1001 commented May 18, 2020

Is this a relatively cleaner implementation of the dvc remote modify oldRemote name newRemote with the same command options as the dvc modify command?

@PseudoNerd
Sorry for the late reply, and thanks to @jorgeorpinel, I'm a little busy last week.
There is no command dvc remote modify name before, renaming the old remote repo is a new feature. And this issue is a documentation update linked to the one in the dvc.

@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented May 18, 2020

@karajan1001 will you be wiling/able to implement this docs update along with your core repo work? Just to know whether to plan to do it ourselves if not (as you can see there is interest from other contributors too). Thanks either way 🙂

@karajan1001
Copy link
Contributor Author

karajan1001 commented May 18, 2020

@jorgeorpinel
@PseudoNerd
Oh, I used to plan to solve it this week, but I am more pleased with other contributor's help.

@jorgeorpinel
Copy link
Contributor

If you're able to do it it's probably the most efficient way since you know exactly how it works. We only need a draft PR on this and we'll fix it up in terms or language etc. so don't worry about it being perfect.

@karajan1001
Copy link
Contributor Author

karajan1001 commented May 18, 2020

@jorgeorpinel
I am just considering writing some introduction to my PR here. A draft PR would be better, and I will finish it soon.

karajan1001 added a commit to karajan1001/dvc.org that referenced this issue May 19, 2020
jorgeorpinel pushed a commit that referenced this issue May 23, 2020
@iesahin iesahin added the C: ref Content of /doc/*-reference label Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: docs Area: user documentation (gatsby-theme-iterative) C: ref Content of /doc/*-reference type: enhancement Something is not clear, small updates, improvement suggestions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants