RomeoAva

Agreed, would it be possible to get a release to implement fixes? For example we are currently unable to use this for `POST` endpoints... Due to: https://github.com/long2ice/fastapi-cache/issues/113 The fix has...

> @RomeoAva please can you try with: > > ```yaml > PYTHON_RUFF_COMMAND_REMOVE_ARGUMENTS: 'check' > PYTHON_RUFF_ARGUMENTS: ['format','--check'] > LOG_LEVEL: DEBUG > ``` > > And see what is the command line...

Hi all, I didn't find a work around using this action unfortunately. I ended up using this Ruff action with something like this: ``` name: Ruff on: workflow_call: jobs: ruff:...

+1 on this. In the past had to handle Bigquery tables outside of Terraform with migrations handled with Alembic. Which made it awkward since everything else was defined in Terraform.....

Hi, I am also facing this same issue. I just started using Sentry and wanted to connect this action to my private Github project. In my project the action is...

I think the issue might be caused by: ``` with: fetch-depth: 0 ``` I am following the documentation: https://github.com/getsentry/action-release?tab=readme-ov-file#usage **Edit**: Nevermind it seems to still be happening even when removed.

> Wrapping just the assets list in `jsonencode` can get through the type validation. Can you try and see? > > ``` > "assets" = jsonencode(["Project_ABC"]) > ``` Hi, like...

> PR has been merged and should be released to the Google provider as part of v5.40.0. A working config would be: > > ``` > resource "google_bigquery_data_transfer_config" "salesforce_config" {...