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

Cant use the git cli #316

Closed
resuta566 opened this issue Jul 28, 2020 · 1 comment
Closed

Cant use the git cli #316

resuta566 opened this issue Jul 28, 2020 · 1 comment

Comments

@resuta566
Copy link

resuta566 commented Jul 28, 2020 •
edited
Loading

Describe the bug

After I upgrade to 2.5.3, I can't use the git CLI any more and have an error

Version & OS

V2.5.3-linux1 , Ubuntu 18.04

Steps to reproduce the behavior

Maybe Upgrade from lower ver from 2.5.3

Expected behavior

Could use the git cli

Actual behavior

I can't

Screenshots

Sreenshot

Logs

2020-07-28T00:01:34.418Z - info: [ui] [AppStore] loading 4 repositories from store
2020-07-28T00:01:34.419Z - info: [ui] [AppStore] found account: resuta566 (James Lester)
2020-07-28T00:01:35.085Z - info: [ui] launching: 2.5.3-linux1 (Linux 5.4.0-42-generic)
2020-07-28T00:01:35.087Z - info: [ui] execPath: '/usr/lib/github-desktop/github-desktop'
2020-07-28T00:03:36.127Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T00:03:39.896Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.757s)
2020-07-28T00:03:40.155Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T00:03:43.443Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.286s)
2020-07-28T00:03:43.529Z - info: [ui] Background fetch for 4 repositories took 8.998sec
2020-07-28T00:18:45.350Z - info: [ui] Background fetch for 4 repositories took 1.818sec
2020-07-28T00:33:44.697Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T00:33:48.011Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.311s)
2020-07-28T00:33:48.268Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T00:33:51.587Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.318s)
2020-07-28T00:33:51.677Z - info: [ui] Background fetch for 4 repositories took 8.148sec
2020-07-28T00:48:45.422Z - info: [ui] Background fetch for 4 repositories took 1.900sec
2020-07-28T01:03:45.083Z - info: [ui] Background fetch for 4 repositories took 1.560sec
2020-07-28T01:18:45.148Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T01:18:48.531Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.379s)
2020-07-28T01:18:48.836Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T01:18:52.252Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.411s)
2020-07-28T01:18:52.345Z - info: [ui] Background fetch for 4 repositories took 8.807sec
2020-07-28T01:33:44.770Z - info: [ui] Background fetch for 4 repositories took 1.248sec
2020-07-28T01:48:44.945Z - info: [ui] Background fetch for 4 repositories took 1.422sec
2020-07-28T02:03:45.361Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T02:03:51.704Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 6.336s)
2020-07-28T02:03:52.000Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T02:03:57.284Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 5.282s)
2020-07-28T02:03:57.365Z - info: [ui] Background fetch for 4 repositories took 13.833sec
2020-07-28T02:18:45.258Z - info: [ui] Background fetch for 4 repositories took 1.731sec
2020-07-28T02:33:44.669Z - info: [ui] Background fetch for 4 repositories took 1.146sec
2020-07-28T02:48:44.696Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T02:48:48.048Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.342s)
2020-07-28T02:48:48.371Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T02:48:51.698Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.315s)
2020-07-28T02:48:51.782Z - info: [ui] Background fetch for 4 repositories took 8.252sec
2020-07-28T03:03:44.663Z - info: [ui] Background fetch for 4 repositories took 1.140sec
2020-07-28T03:18:45.109Z - info: [ui] Background fetch for 4 repositories took 1.586sec
2020-07-28T03:33:45.069Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T03:33:48.352Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.280s)
2020-07-28T03:33:48.649Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T03:33:51.959Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.309s)
2020-07-28T03:33:52.049Z - info: [ui] Background fetch for 4 repositories took 8.513sec
2020-07-28T03:48:45.433Z - info: [ui] Background fetch for 4 repositories took 1.910sec
2020-07-28T04:01:36.220Z - info: [ui] Stats reported.
2020-07-28T04:03:44.723Z - info: [ui] Background fetch for 4 repositories took 1.200sec
2020-07-28T04:18:44.650Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T04:18:48.641Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.987s)
2020-07-28T04:18:48.806Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T04:18:52.256Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.450s)
2020-07-28T04:18:52.346Z - info: [ui] Background fetch for 4 repositories took 8.817sec
2020-07-28T04:33:47.584Z - info: [ui] Background fetch for 4 repositories took 4.062sec
2020-07-28T04:48:44.667Z - info: [ui] Background fetch for 4 repositories took 1.144sec
2020-07-28T05:03:44.715Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T05:03:48.039Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.321s)
2020-07-28T05:03:48.187Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T05:03:51.568Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.377s)
2020-07-28T05:03:51.650Z - info: [ui] Background fetch for 4 repositories took 8.120sec
2020-07-28T05:18:44.789Z - info: [ui] Background fetch for 4 repositories took 1.267sec
2020-07-28T05:33:44.724Z - info: [ui] Background fetch for 4 repositories took 1.201sec
2020-07-28T05:48:44.665Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T05:48:48.175Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.505s)
2020-07-28T05:48:48.323Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T05:48:51.575Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.249s)
2020-07-28T05:48:51.656Z - info: [ui] Background fetch for 4 repositories took 8.125sec
2020-07-28T06:03:44.764Z - info: [ui] Background fetch for 4 repositories took 1.241sec
2020-07-28T06:18:45.221Z - info: [ui] Background fetch for 4 repositories took 1.698sec
2020-07-28T06:33:47.753Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T06:33:56.074Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 8.316s)
2020-07-28T06:33:56.404Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T06:34:13.139Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 16.733s)
2020-07-28T06:34:13.247Z - info: [ui] Background fetch for 4 repositories took 29.716sec
2020-07-28T06:48:45.251Z - info: [ui] Background fetch for 4 repositories took 1.728sec
2020-07-28T07:03:57.630Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T07:04:30.270Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 32.636s)
2020-07-28T07:04:30.411Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T07:06:05.603Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 95.182s)
2020-07-28T07:06:05.688Z - info: [ui] Background fetch for 4 repositories took 142.159sec
2020-07-28T07:18:44.728Z - info: [ui] Background fetch for 4 repositories took 1.206sec
2020-07-28T07:33:44.698Z - info: [ui] Background fetch for 4 repositories took 1.175sec
2020-07-28T07:48:44.832Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T07:48:48.469Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.634s)
2020-07-28T07:48:48.990Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T07:48:52.179Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.187s)
2020-07-28T07:48:52.291Z - info: [ui] Background fetch for 4 repositories took 8.762sec
2020-07-28T08:04:04.924Z - info: [ui] Background fetch for 4 repositories took 21.402sec
2020-07-28T08:18:44.669Z - info: [ui] Background fetch for 4 repositories took 1.146sec
2020-07-28T08:33:44.720Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T08:33:48.725Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 4.005s)
2020-07-28T08:33:48.926Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T08:33:52.444Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.516s)
2020-07-28T08:33:52.543Z - info: [ui] Background fetch for 4 repositories took 9.015sec
2020-07-28T08:48:44.748Z - info: [ui] Background fetch for 4 repositories took 1.225sec
2020-07-28T09:03:51.909Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:04:05.755Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 13.841s)
2020-07-28T09:04:06.251Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:04:27.156Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 20.904s)
2020-07-28T09:04:27.255Z - info: [ui] Background fetch for 4 repositories took 43.727sec
2020-07-28T09:08:44.545Z - info: [ui] [Timing] Action 'create commit' for 'admin-job-order' took 0.409s
2020-07-28T09:08:45.252Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:08:49.614Z - info: [ui] Executing push: git -c credential.helper= push origin development:development --progress (took 4.356s)
2020-07-28T09:08:49.615Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:08:52.968Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.353s)
2020-07-28T09:16:00.641Z - info: [ui] [Timing] Action 'create commit' for 'admin-job-order' took 0.391s
2020-07-28T09:16:02.231Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:16:09.057Z - info: [ui] Executing push: git -c credential.helper= push origin development:development --progress (took 6.825s)
2020-07-28T09:16:09.057Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:16:12.383Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.325s)
2020-07-28T09:18:47.556Z - info: [ui] Background fetch for 4 repositories took 4.025sec
2020-07-28T09:20:17.929Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:20:21.479Z - info: [ui] Executing push: git -c credential.helper= push origin development:development --progress (took 3.547s)
2020-07-28T09:20:21.479Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:20:24.701Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.220s)
2020-07-28T09:20:30.421Z - info: [ui] [Timing] Action 'create commit' for 'admin-job-order' took 0.356s
2020-07-28T09:27:30.473Z - info: [ui] [Timing] Action 'create commit' for 'admin-job-order' took 0.323s
2020-07-28T09:27:31.809Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:27:35.624Z - info: [ui] Executing push: git -c credential.helper= push origin development:development --progress (took 3.812s)
2020-07-28T09:27:35.625Z - info: [ui] proxy url not resolved, protocol not supported
2020-07-28T09:27:39.047Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune origin (took 3.409s)
2020-07-28T09:33:53.595Z - warn: [ui] fetchRepository: an error occurred for 'resuta566/coolmart'
TypeError: Failed to fetch
2020-07-28T09:34:07.268Z - info: [ui] Background fetch for 4 repositories took 23.735sec
2020-07-28T09:39:29.146Z - info: [ui] Executing fetch: git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin (took 3.039s)
2020-07-28T09:40:36.236Z - info: [ui] Executing fetch: git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin (took 4.047s)
@shiftkey
Copy link
Owner

@resuta566 thanks for the feedback!

GitHub Desktop does not include the Git command line tool, and the version embedded in the app is not intended for general use. I would recommend installing this PPA which gives you access to the latest Git releases for Ubuntu.

shiftkey pushed a commit that referenced this issue Apr 14, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
2f96aaf 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 15, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
927a0b6 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 15, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
927b6b2 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 15, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
afc9abc 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 15, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
3a26a90 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 15, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
22a7fda 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 15, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
81ea317 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 21, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
7a45520 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 21, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
fb531c9 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 21, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
2fcb2c0 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 25, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
fc0dcd7 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 27, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
fca29a3 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 27, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
448da93 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Apr 27, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
4309d17 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue May 25, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
b05ff2b 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jun 11, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
1051d66 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jun 11, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
211f2ec 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jun 11, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
22ce720 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jun 25, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
5f9b25d 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jun 25, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
1e19b33 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jun 25, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
642105f 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 6, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
3ce325d 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 6, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
7f0a959 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 6, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
82948b4 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 26, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
4cf323c 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 26, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
0973a75 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 26, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
c9c2b42 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 26, 2022
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
80e94f4 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 1, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
e5f9084 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Jul 13, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
f712bb5 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 10, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
04fc363 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 10, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
af86f7f 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 10, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
1cac122 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
e72a60d 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
7e3f20c 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
1dee735 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
16ccdc1 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
6b794c1 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
762764b 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
9b7feb2 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
083fd2b 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
1fcadce 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
e23cf8d 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
f9d29d3 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
eafcfb4 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
f8a49c4 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
allow tilde character when specifying a local repository (#316)
bd476ee 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
d0d8fda 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
b74f69b 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 11, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
911c679 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 12, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
2c208dc 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 12, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
dc55fca 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 14, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
0d27ef1 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 15, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
8d3f765 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 17, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
6e68e81 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Aug 17, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
ab5df70 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Sep 2, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
19a96cf 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
shiftkey pushed a commit that referenced this issue Sep 2, 2024
@Daniel-McCarthy @shiftkey
fix: allow tilde character when specifying a local repository (#316)
8ae3055 
There already exists a function that will convert a tilde path to an absolute path. It was originally used for this purpose, but the functionality was removed during a commit that changed which function was used to validate git repositories.

This reinstates that functionality and allows us to type a ~/ tilde path to get our home directories when typing in a path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shiftkey @resuta566