Re: Question: What is the best practice regarding remote names

It doesn't really matter, but the remote for your fork (or the main repo,
if you work directly on a branch of the main repo like me) is usually named
origin.

Am Di., 23. Juni 2026 um 13:45 Uhr schrieb Patrick Callahan <
[email protected]>:

> This is a bit of a nit.
>
> While I got my git skills up to speed, I found the term origin a bit
> confusing so I named the remotes to my forks with my username. (It works,
> but it's probably not what everyone else does)
>
> I want my local practices to match what an experienced flightgear dev
> would normally do.
>
> What's your answer to:
>
> cd flightgear; git remote -v?
>
> -Pat
>
> Mine is currently:
>
> $worktree flightgear next
> cd /owc/worktrees/flightgear.next
> $git remote -v
> callahanp [email protected]:callahanp/flightgear.git (fetch)
> callahanp [email protected]:callahanp/flightgear.git (push)
> upstream https://gitlab.com/flightgear/flightgear.git (fetch)
> upstream no-push (push)
>
> I'm thinking it shoulduse the name origin for the fork.  Is this correct?
>
> origin [email protected]:callahanp/flightgear.git (fetch)
> origin [email protected]:callahanp/flightgear.git (push)
> upstream https://gitlab.com/flightgear/flightgear.git (fetch)
> upstream no-push (push)
>
> My current workflow is to pull from upstream next and upstream 2024.1 and
> then push to callahanp, then rebase any feature/fix branches on upstream
> next
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel