-
Notifications
You must be signed in to change notification settings - Fork 22
Cleanup CI #147
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
base: main
Are you sure you want to change the base?
Cleanup CI #147
Conversation
@@ -19,48 +19,14 @@ jobs: | |||
- name: Checkout | |||
uses: actions/checkout@v4 | |||
|
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.
I'm trying to understand what exactly this workflow is doing.
Is this workflow only ran when user manually trigger it? If that is the case, do we really need to Upload export artifact
step? Are any other jobs using the artifacts? Or it's just for people to download the artifacts?
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.
The workflow is designed so that people can get development dependencies without building them on their local computer. I put this as the recommended way to do it due to me having many problems trying to locally build the dependencies when I was starting development. It is only run when users trigger it, and the uploaded artifacts are only for them.
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.
Left a non-blocking comment.
But LGTM overall.
fixes #146
Reduces code duplication in workflows.