Re: [yocto-patches] [yocto-autobuilder-helper][PATCH] prepare-shared-repos: Allow to tag poky git

[Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>]

On Fri, Nov 15, 2024 at 03:21:15PM +0100, Quentin Schulz wrote:
> Hi Mathieu,
> 
> Apparently git-push supports pushing without a remote, c.f. the manpage:
> 
>        git push [--all | --branches | --mirror | --tags] [--follow-tags]
> [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
>                   [--repo=<repository>] [-f | --force] [-d | --delete]
> [--prune] [-q | --quiet] [-v | --verbose]
>                   [-u | --set-upstream] [-o <string> |
> --push-option=<string>]
>                   [--[no-]signed|--signed=(true|false|if-asked)]
>                   [--force-with-lease[=<refname>[:<expect>]]
> [--force-if-includes]]
>                   [--no-verify] [<repository> [<refspec>...]]
> 
> [...]
> 
>        <repository>
>            The "remote" repository that is the destination of a push
> operation. This parameter can be either a URL (see the section GIT URLS
> below) or the name of a remote (see the section REMOTES below).

Oh, that's nice! I was definitely not aware of this possibility. I will
send a new version.

> 
> This would avoid leftovers from stopped/interrupted/broken runs to mess with
> the git remote addition which could fail if the remote already exists.
> 

Um right, I did not think about builds potentially interrupted in the
mean time, thanks.

> Either don't use an explicit local remote, or remove it beforehand. Except
> that removing a non-existing remote will fail check_call, so you probably
> want to simply run the command and ignore the return code.
> 
> Cheers,
> Quentin

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com