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.

Sign up for GitHub

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

Jump to bottom

[Feature]: Add possibility to use other git remote than origin #37

Closed
1 task done
mengdaming opened this issue Feb 16, 2022 · 0 comments · Fixed by #793
Closed
1 task done

[Feature]: Add possibility to use other git remote than origin #37

mengdaming opened this issue Feb 16, 2022 · 0 comments · Fixed by #793
Assignees
@mengdaming
Labels
enhancement New feature or request M Medium

Comments

@mengdaming
Copy link
Contributor

Contact Details

damien.menanteau@gmail.com

Feature Request

TCR currently uses origin git remote when processing git push/pull operations. Although it works in majority of cases as origin is created automatically when cloning a repository, there can be situations where it fails:

  • when the user renamed origin to something else
  • when the user removed origin

Feature Description

Add a new CLI parameter / configuration setting allowing to specify the name of the git remote.

If this setting is not specified, TCR will use origin as the default value

Alternatives

  • Add a warning in the README to inform the user that they must have git remote origin properly set in order to run TCR
  • Enforce this by a checkpoint in tcr check

Additional Context

N/A

Code of Conduct

  • I agree to follow this project's Code of Conduct
@mengdaming mengdaming added the enhancement New feature or request label Feb 16, 2022
@mengdaming mengdaming added the M Medium label Oct 19, 2022
@mengdaming mengdaming self-assigned this Oct 1, 2024
mengdaming added a commit that referenced this issue Oct 2, 2024
@mengdaming
[#37] Add git-remote CLI flag and related plumbing
c99c2ba
mengdaming added a commit that referenced this issue Oct 2, 2024
@mengdaming
[#37] Add git remote name as an argument to git VCS initializer
1411eb3 
- add checker warning when git remote name is not found
- rollback adding ot SetRemoteName() to VCS interface
- remove constant DefaultRemoteName from git implementation
- update git.SessionSummary() so that it also provides the remote name when available
mengdaming added a commit that referenced this issue Oct 2, 2024
@mengdaming
[#37] Update TCR help doc with new option -g/--git-remote
25601aa
@mengdaming mengdaming mentioned this issue Oct 2, 2024
Merged
5 tasks
@mengdaming mengdaming linked a pull request Oct 2, 2024 that will close this issue
Add possibility to use a git remote other than "origin" #793
Merged
5 tasks
mengdaming added a commit that referenced this issue Oct 11, 2024
@mengdaming
[#37] Add git-remote CLI flag and related plumbing
40d374b
mengdaming added a commit that referenced this issue Oct 11, 2024
@mengdaming
[#37] Add git remote name as an argument to git VCS initializer
728fa60 
- add checker warning when git remote name is not found
- rollback adding ot SetRemoteName() to VCS interface
- remove constant DefaultRemoteName from git implementation
- update git.SessionSummary() so that it also provides the remote name when available
mengdaming added a commit that referenced this issue Oct 11, 2024
@mengdaming
[#37] Update TCR help doc with new option -g/--git-remote
c86d72d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mengdaming mengdaming

Labels
enhancement New feature or request M Medium
Projects
TCR Enhancements & Bugs Follow Up
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add possibility to use a git remote other than "origin" murex/TCR
1 participant
@mengdaming