Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

running the action in parallel #42

Open
leksmano opened this issue Dec 16, 2022 · 0 comments
Open

running the action in parallel #42

leksmano opened this issue Dec 16, 2022 · 0 comments

Comments

@leksmano
Copy link

Currently if multiple github actions are executed in parallel they appear to all use the same CHECK_NAME

const blackduckPolicyCheck = await createCheck(CHECK_NAME)

I wanted to find out if there is a reason for this?

This appears to cause the results to be overwritten in the PR overview screen, and all results seem to be appended in the same "Black Duck Policy Check" check.

Should it be possible to allow specifying an optional CHECK_NAME prefix that would allow unique names to be created?

similar to how other inputs are provided here:

export const SCAN_MODE = getInput('scan-mode').toUpperCase()

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

No branches or pull requests

1 participant