You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if we should somehow skip that part. If we ever need to update the existing keys before an update we can always push out a new installer and update the action to use it. I haven't thought about how to skip it yet.
The text was updated successfully, but these errors were encountered:
Continuing my journey to nitpick everything. I hope that's OK.
It's absolutely ok!
I wonder if we should somehow skip that part. If we ever need to update the existing keys before an update we can always push out a new installer and update the action to use it. I haven't thought about how to skip it yet.
Maybe we should have some environment variable to customize this and other similar details. That would allow to skip all of them, but force the "default" behaviour when we need it. From the Action, we can decide when to set/unset that variable by checking some api/file/release. I guess any API call will take a second.
Moreover, skipping these kind of checks can be the default behaviour when CI is set. Then, we can use FULL_CI, FORCE_CHECKS, FULL_UPDATE to force them.
Continuing my journey to nitpick everything. I hope that's OK.
So, on the first start we have:
Which means 11 seconds lost for basically no change. (the thing executed here is this I think: https://github.com/msys2/MSYS2-packages/blob/3a99587ca16686fd0e2e74ffacabd2be15dd85ae/filesystem/07-pacman-key.post#L7)
I wonder if we should somehow skip that part. If we ever need to update the existing keys before an update we can always push out a new installer and update the action to use it. I haven't thought about how to skip it yet.
The text was updated successfully, but these errors were encountered: