I want a "rebase and run ci and merge, but in a new branch" button

so https://blog.jetbrains.com/space/2023/04/18/space-git-flow/?

why so you post such things at 10pm

now I need to read it!

soriiiiiiiiiiiiiiiiiiiiii

:P

liar!

(I also had posted that in that other chat thingy back when this was published, so it's not exactly new to you maybe :P)

github has this rebase option, but it does a force push and when the branch comes from another namespace, that sucks

I am bad at keeping track of discord

or anything that is not this channel

:D

o/

bastelfreak: you mean the backtrace?

yeah

Hmm, I can't find how we can exit with non-null value and not display a backtrace. My search-engine-foo does not help :-/

well, `ex

exit 1

does the right thing…

bastelfreak: https://github.com/voxpupuli/voxpupuli-release/pull/52 does it help?

looks good

@bastelfreak regarding the archive module, we are seeing in SLES deployments of influxdb module having ensure present, and cleanup true causes a constant download and delete cycle

archive { '/tmp/influxdb.tar.gz':
      ensure          => present,
      extract         => true,
      extract_command => 'tar xfz %s --strip-components=1',
      extract_path    => '/opt/influxdb',
      source          => $archive_source,
      cleanup         => true,
      require         => File['/etc/influxdb', '/opt/influxdb'],
      before          => Service['influxdb'],
    }

isn't that missing a

creates

?

ill see if i can do a simple repro and then raise an issue for the module

OR it could be we did something like that wrong :0

ah ok, so adding a creates in will prevent the need for a future download and break the cycle?

ok thats makes sense, its basically a built in onlyif

https://github.com/voxpupuli/puppet-prometheus/blob/master/manifests/daemon.pp#L108-L120 as example

OK cool that makes more sense and we can fix that this morning! cheers i may do a pr for the docs as i cant see a link between those two parameters really described anywhere and that could trip people like us up 🙂

how do you expect that puppet tracks the archive when you cleanup the archive? 🙂

yeah it 100% makes sense when you explain it 🙂