Skip to content

Conversation

@widhalmt
Copy link
Member

@widhalmt widhalmt commented Nov 5, 2024

Introduce 2 new incidents that will trigger a KICS (security scan) run:

This will fix the fact that KICS only runs on Pull Requests but does not work as code scanning utility the way GitHub means it.

@widhalmt widhalmt added the bug Something isn't working label Nov 5, 2024
@widhalmt widhalmt self-assigned this Nov 5, 2024
@widhalmt
Copy link
Member Author

widhalmt commented Nov 5, 2024

Looking at the tests that ran I see KICS two times. Once for the push and once for the pull request. What do you think how should we get rid of one of the tests? Just use push?

@tbauriedel tbauriedel enabled auto-merge November 5, 2024 12:30
@tbauriedel tbauriedel disabled auto-merge November 5, 2024 12:31
@tbauriedel
Copy link
Contributor

tbauriedel commented Nov 5, 2024

I would not add it to push.
Since we enforce users to create a PR, it should be enough to run that job on PRs and cron-based for main.

As you can see in this PR, the action is triggered twice. One for push and one for PR.

@widhalmt widhalmt added this pull request to the merge queue Nov 5, 2024
Merged via the queue into main with commit 3c7a91b Nov 5, 2024
10 checks passed
@widhalmt widhalmt deleted the fix/schedule-for-kics branch November 5, 2024 15:27
ivareri pushed a commit to ivareri/ansible-collection-elasticstack that referenced this pull request Jun 17, 2025
Introduce 2 new incidents that will trigger a KICS (security scan) run:

* Weekly scheduled by cron
* On every `push`. We can rework that later. But it should be the
fastest way of getting results into
https://github.com/NETWAYS/ansible-collection-elasticstack/security
right now. Which will help with assigning tasks.

This will fix the fact that KICS only runs on Pull Requests but does not
work as code scanning utility the way GitHub means it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants