Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Strange placement of [container-scan] action in actions page
See original GitHub issueHi,
I have been using this action in my project CI: here you container-scan is called within Docker workflow. However, I start noticing that if you go through my commit history, I start seeing container-scan showing up under other workflows. Take this one for example, why is [container-scan] falls under Node CI in this case. You can also check other commits’ CI pipeline and you would not find [container-scan] under Docker workflow like intended. Am I doing something wrong?
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @akphi, I have raised this issue internally and it is being discussed. The source of the issue is the tight coupling between check runs and actions service. At this point, it is not clear how this problem can be solved. I will update this issue when I get more details.
Sure thing! I don’t quite get the explanation, but I take it as a
won't-fixfor now. I will try outscanitizeras you recommended. My question is though, currently I setup the scan in a github actions, if I installscanitizer, do I need to remove that action or so?Also, would be great if we could have some more documentation for the app 😭