Time |
Nick |
Message |
01:16 |
|
calcul0n__ joined #minetest-hub |
04:00 |
|
MTDiscord joined #minetest-hub |
08:00 |
|
ShadowNinja joined #minetest-hub |
09:44 |
|
Fixer joined #minetest-hub |
10:53 |
|
Fixer_ joined #minetest-hub |
10:54 |
|
calcul0n__ joined #minetest-hub |
11:52 |
|
calcul0n joined #minetest-hub |
12:03 |
Krock |
deprecation notice from github about password-based pushes: *exists* |
12:03 |
Krock |
me: I'll ignore that. |
12:04 |
Krock |
I'd appreciate it if there's a way to password-protect pushes to upstream though. SSH/keys are nice but they increase the oopsie potential |
12:04 |
|
Fixer joined #minetest-hub |
12:04 |
Krock |
tips are welcome :) |
12:04 |
sfan5 |
use a passworded ssh key |
12:05 |
Krock |
well, after using it once, the key is unlocked for the session. at least that applies to my VPS key |
12:09 |
sfan5 |
hm yea |
12:09 |
sfan5 |
I believe desktop session set up an ssh agent for you that does this |
12:09 |
sfan5 |
could probably disable it for a specific key? or for github.com? |
12:16 |
Krock |
yet nothing found in man ssh-agent |
12:16 |
|
calcul0n joined #minetest-hub |
12:19 |
sfan5 |
try man ssh_config |
12:19 |
Krock |
either everything or nothing is cached, depending on whether ssh-agent is running |
12:20 |
Krock |
err yes, I grepped "man ssh_config", not "man ssh-agent" |
12:22 |
Krock |
per-key-caches can be removed using `ssh-add -d filepath`, or all of them using `ssh-add -D` |
15:02 |
|
Toothless joined #minetest-hub |
15:02 |
|
calcul0n_ joined #minetest-hub |
15:29 |
|
Toothless joined #minetest-hub |
16:20 |
|
hlqkj joined #minetest-hub |
18:45 |
celeron55_ |
git could have a "confirm pushes" client side option... maybe it doesn't |
18:47 |
celeron55_ |
a pre-push hook? |
18:51 |
Krock |
celeron55_: interesting idea. thank you. I found https://gist.github.com/mosra/19abea23cdf6b82ce891c9410612e7e1 and that seems to be a pretty good start |
19:11 |
|
Toothless joined #minetest-hub |
19:37 |
MTDiscord |
<Benrob0329> Does Github not have protected branches? |
19:39 |
Krock |
@Benrob0329 protected branches are about force-pushing |
19:48 |
sfan5 |
I think you can also protect branches so that only approved PRs can be merged into it |
19:48 |
sfan5 |
but this is not what we want |
23:44 |
rubenwardy |
You can also protect branches to only push from PRs, approved or not |