Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

v3 action check fails #284

Closed
mexikoedi opened this issue Nov 30, 2024 · 2 comments
Closed

v3 action check fails #284

mexikoedi opened this issue Nov 30, 2024 · 2 comments

Comments

@mexikoedi
Copy link

mexikoedi commented Nov 30, 2024

What events trigger your workflow?

on: push

What OS does your workflow use?

runs-on: ubuntu-latest

How is cpp-linter-action configured?

- uses: actions/checkout@v4.2.2
- uses: cpp-linter/cpp-linter-action@v3
  id: linter
  env:
       GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  with:
       style: file

What was the unexpected behavior?

I am using this action in a repository and cpp-linter-action@v2 was updated to cpp-linter-action@v3 by dependabot and now the check fails. I didn't change anything else and the error which appears doesn't help either.
I get the following error: error: a value is required for '--database <database>' but none was supplied.
Which happens after Run source "$GITHUB_ACTION_PATH/venv/bin/activate.
Do I need to configure something or how can I fix this issue?
I couldn't find any information for v3 or this error.

@2bndy5
Copy link
Collaborator

2bndy5 commented Nov 30, 2024

v3 is a branch, not a tag. We are not ready to deploy v3.

I am using this action in a repository and cpp-linter-action@v2 was updated to cpp-linter-action@v3 by dependabot and now the check fails.

This is troubling. I'll rename the branch. Please switch back to v2

@mexikoedi
Copy link
Author

v3 is a branch, not a tag. We are not ready to deploy v3.

I am using this action in a repository and cpp-linter-action@v2 was updated to cpp-linter-action@v3 by dependabot and now the check fails.

This is troubling. I'll rename the branch. Please switch back to v2

Ah ok, that's why I couldn't find anything about it.
I close this issue then, thanks for the heads up, switched back.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants