-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
New Github action added for cli #1487
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
@asyncapi/bounty_team |
github-action/lib/index.js
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akshatnema this has been already changed and we are using bash script right now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, it's not needed in action, now right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, you have to add the bash script.
# Create a non-root user | ||
RUN addgroup -S myuser && adduser -S myuser -G myuser | ||
|
||
RUN apk add --no-cache bash>5.1.16 git>2.42.0 chromium |
Check notice
Code scanning / SonarCloud
Arguments in long RUN instructions should be sorted Low
/u |
@akshatnema any blockers being faced by you? |
Quality Gate failedFailed conditions |
There is no update as I'm researching around the fact on how to manage GitHub Action for CLI. @Shurtu-gal and @derberg proposals require different configurations, which in fact means we need to have the same package.json for both CLI and it's respective GitHub action. I'm currently looking at how to use only one configuration and one package.json. Although the matter looks simple, it will take time to try different approaches, so if I don't achieve a break-through in the nearest couple of days, I'll ask for the Timeline Extension. |
but the GH action do not need package.json as it is bash and docker based only. So no need for monorepo afaik - I think we talked about it |
@derberg @Shurtu-gal ok so should we do it in a manner that we completely remove the package.json from github action? Since, there is no need of a separate package.json, our whole github action depends on the working of |
That's correct. If I remember correctly the package.json was there just to support the workflows already present. |
Description
Draft PR to add the github action for cli from https://github.com/asyncapi/github-action-for-cli.
Related issue(s)
asyncapi/github-action-for-cli#396