nolange

> How should gitlab-ci-local determine which of your two remotes to use exactly ? Look at the current branch, see it it has an upstream branch (default push/pull target). If...

If you are in a git repository, you get the upstream branch (or an error message if there is none) with: ``` bash git rev-parse --abbrev-ref @{upstream} ``` would return...

It should automatically work for most setups, without tinkering. 1. Only one remote -> no issue 2. Upstream branch configured (as is usually the case in most setups) > use...

> Use this `git rev-parse --abbrev-ref @{upstream} | cut -d / -f1 | xargs -I {} git remote get-url {}` to auto detect remote url. Basically, yes - but do...

i think i ran into this aswell. > I am unsure about 64bit. It would significantly slow down calculations on 32bit machines, but maybe we dont care. what are you...

There seems to be a bug with argument parsing, calling the mergetool like its documented will try to find a git repo in the applications path (and above). Look at...

> > "internal" stuff gets into clangs internal library, ex: lib/clang/18/lib/windows/lib/libclang_rt.asan_dynamic-x86_64.dll > > I really don't see the need for this... I thought llvm-mingw distributions are intended to be standalone...

I experimented with this as well, I used the lookup strategy to separate configs for compiler-type and target. UWP would require a different triple (`armv7-w64-windows-gnuuwp-clang`for example). Otherwise, symlinks to clang...

I am using Linux (debian bookworm x86_64).

> ``` > systemd.unified_cgroup_hierarchy > > When specified without an argument or with a true argument, enables the usage of > unified cgroup hierarchy (a.k.a. cgroups-v2). When specified with a...