Patch update process

[farfromrefug]

I am trying to build 1.67 nightly because 1.66 have an known CPU usage issue which should be fixed in 1.67. And my computer is burning out right now ...
Now the build fails because one patch is not up to date anymore. I am ok with fixing it and creating a PR but i dont know what the process is to update a patch ?
Could someone guide me? We could even add it to the readme, it could help contributions

[daiyam]

@farfromrefug Hi, here are my steps:

• run ./build/build_linux.sh, if a patch is failing then,
• open vscode directory in vscodium
• revert all changes
• run git apply --reject ../patches/use-github-pat.patch
• fix *.rej
• run yarn watch
• run ./script/code.sh until everything ok
• run git diff > ../patches/use-github-pat.patch

[daiyam]

I was thinking to release some vscodium-insiders but I'm afraid we might run into the quota of the actions runtime.
I will need to finish #960...

Edit: I'm stupid: "Minutes are free for public repositories." I've just had to look at the little lines...

[farfromrefug]

@daiyam you are right i actually disable most workflow triggers for my use case.
And what about a weekly insider for a start? it is like 4 times faster that vscode release process. Or maybe twice a week

EDIT: why do you have the workflows running on every commit? https://github.com/VSCodium/vscodium/blob/master/.github/workflows/macos.yml#L7= (if read it correctly)

[daiyam]

@farfromrefug No quota for public repositories. cf my edit...

Anyway, I was thinking about a weekly release.

[paulcarroty]

Weekly seems fine. Maybe worth to add the parching guide^ to insiders README.

[daiyam]

I've started a new discussion about the Insiders version at #1057.