Cannot disable boolean options with default value true like --pull and --rebuild

[ChristopherHX]

Github Local Actions Version

dev

Act Version

0.2.70

GitHub Repository Link

N/A

Workflow Content

N/A

Act Command Used

N/A

Act Command Output

N/A

Bug Description

Related to discussions in #117

Until nektos/act#2522 would be merged we cannot disable --pull and --rebuild using your GUI.

While at the moment I think this will not happen at all.

Usage is --pull=false to explicitly disable them and not using default true

getAllOptions() will have default value set to true for them.

I had to make a breaking change to the default docker images in 2023 and forcing everyone to update their image was easier than handling the possible bug reports of broken images.
Changing defaults is less breaking than renaming the options to contain negation in it's name.

Act Bug Report

N/A

[ChristopherHX]

for options of type bool, having "true" or "false" as only selectable values in edit could help while =true can be omitted on the cli like today.

Alternatively passing options with default true if disabled via checkbox with value false and keep current behavior for normal options.

[aliuq]

Sometimes you will encounter the following error. Can we set pull to false to prevent forcePull=true?

Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout

[ChristopherHX]

Can we set pull to false to prevent forcePull=true?

You should be able to put...

--pull=false

...into a file called $PWD/.actrc as a new line

Use --bug-report of the act cli to see the operating system specific global file location

Sometimes you will encounter the following error.

I don't remember to have ever seen your error in act.

You can technically just append space + --pull=false to the act command setting...

[SanjulaGanepola]

I will be revisiting the current PR we have open (#117) this weekend to better support this.

[ChristopherHX]

No open PR from my side implement this, the removal of the default value of type bool during review restored this issue with both experimental act (--list-options) and regular act

...and yes I refused to look into implementing further improvements