fix: initialize git submodules in CI build workflow - #129

'bool' does not contain a definition for 'IsAvailableForReuse' and no accessible extension method 'IsAvailableForReuse' accepting a first argument of type 'bool' could be found (are you missing a using directive or an assembly reference?)

In language version 14.0, 'field' is a keyword within a property accessor. Rename the variable or use the identifier '@field' instead.

'bool' does not contain a definition for 'IsAvailableForReuse' and no accessible extension method 'IsAvailableForReuse' accepting a first argument of type 'bool' could be found (are you missing a using directive or an assembly reference?)

In language version 14.0, 'field' is a keyword within a property accessor. Rename the variable or use the identifier '@field' instead.

'bool' does not contain a definition for 'IsAvailableForReuse' and no accessible extension method 'IsAvailableForReuse' accepting a first argument of type 'bool' could be found (are you missing a using directive or an assembly reference?)

In language version 14.0, 'field' is a keyword within a property accessor. Rename the variable or use the identifier '@field' instead.

'bool' does not contain a definition for 'IsAvailableForReuse' and no accessible extension method 'IsAvailableForReuse' accepting a first argument of type 'bool' could be found (are you missing a using directive or an assembly reference?)

In language version 14.0, 'field' is a keyword within a property accessor. Rename the variable or use the identifier '@field' instead.

'bool' does not contain a definition for 'IsAvailableForReuse' and no accessible extension method 'IsAvailableForReuse' accepting a first argument of type 'bool' could be found (are you missing a using directive or an assembly reference?)

In language version 14.0, 'field' is a keyword within a property accessor. Rename the variable or use the identifier '@field' instead.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-dotnet@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.

In language version 14.0, the 'field' keyword binds to a synthesized backing field for the property. To avoid generating a synthesized backing field, and to refer to the existing member, use 'this.field' or '@field' instead.