-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
[IDEA] feat: GitHub-Action #473
Comments
Ok, so a little bit of context Im currently implementing some workflows and I noticed that 2 of the tools that I need didn't have an github action, if you look into https://github.com/marketplace?type=actions&query=cyclonedx+ you will see that there are a few tools/plugins that have an action for this. As for pros and cons I see the following.
|
re: #473 (comment)
Please help me understand the benefit for the users of such an action. |
Thats fair @jkowalleck it doesn't really make sense. Im going to close the PR, sorry for wasting your time |
No worries, @fnxpt. I will keep this feature request open. |
Closed, in favor of CycloneDX/gh-node-module-generatebom#6 |
A pull request #472 was opened out of nowhere,
that suggested having a GitHub-Action that installs and runs this very tool.
This is an arguable topic, so let's discuss:
Why is such a GH-Action needed?
What are the actual use cases? How would you use it?
What are the pros? What are the cons?
What is the benefit of a GH-Action instead of running the installation process and the tool via a GitHub-Workflow yourself?
... and much more .
The text was updated successfully, but these errors were encountered: