cpp-linter workflows runs for every change

[shenxianpeng]

I guess your change here was to disable all cpp-linter runs only run when there is a change under docs/examples/demo/

cpp-linter-action/.github/workflows/cpp-linter.yml

Line 6 in 7ce9dc2

- "!**"

but right now, it seems cpp-linter runs and adds comments for everything. see 7ce9dc2#comments

[2bndy5]

yes, that was the idea. But it didn't seem to work as expected. Maybe if we just remove that line, it would only run when there are changes to the demo sources.

github docs for on.<event>.path

Currently we are only using that workflow to show an example badge in the README. We don't often modify the demo sources. So, how useful it is to even have both the CI workflow and the demo sources in this repo?

[shenxianpeng]

yes, that was the idea. But it didn't seem to work as expected. Maybe if we just remove that line, it would only run when there are changes to the demo sources.

I think just remove it should be work.

[2bndy5]

We should also disable thread-comments for that workflow. That way we are less bothered by the posted comment.

[shenxianpeng]

Currently we are only using that workflow to show an example badge in the README. We don't often modify the demo sources. So, how useful it is to even have both the CI workflow and the demo sources in this repo?

Right. leave it there could as user's actual example and an example badge

[2bndy5]

It might be getting triggered from master branch not main branch.

[2bndy5]

Oh, I see. Actually, the comment comes from the test CI workflow which calls the test repo's reusable workflow.

So, maybe we don't run the test CI on push events?

[shenxianpeng]

So, maybe we don't run the test CI on push events?

That should be fine.

[2bndy5]

yep. that fixed it 🎉

[2bndy5]

That change in 57cc38b might also fix the problem where the latest tag was pointing to the PR's base branch tip (instead of the PR's head branch tip).