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

Add dist-check workflow #99

Closed
wants to merge 4 commits into from
Closed

Add dist-check workflow #99

wants to merge 4 commits into from

Conversation

fmulero
Copy link
Contributor

@fmulero fmulero commented Oct 27, 2022

Signed-off-by: Fran Mulero fmulero@vmware.com

Description of the change

Follow the same approach as in https://github.com/actions/ with the dist folder. Users has to maintain that folder and the workflow checks the content

Additional information

Execution example: fmulero#1

Signed-off-by: Fran Mulero <fmulero@vmware.com>
Signed-off-by: Fran Mulero <fmulero@vmware.com>
Signed-off-by: Fran Mulero <fmulero@vmware.com>
Copy link
Contributor

@Mauraza Mauraza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mpermar
Copy link
Contributor

mpermar commented Oct 27, 2022

A bit confused here, I think that is the same approach we are following today. The only difference I can spot (apart from the cache, which I'm not sure if we need) is that when the diff fails a new artifact gets uploaded.

@fmulero
Copy link
Contributor Author

fmulero commented Oct 27, 2022

You right, I didn't see that validation, so this PR is not adding any value.

To be honest having the dist folder as part of the code seems a little bit weird but I it should be at least autogenerated, but I didn't see a clean way to do it, because it will change the PR status continuously, maybe that's the reason why github guys added the same validation.

Thanks @mpermar I am going to close the PR

@fmulero fmulero closed this Oct 27, 2022
@fmulero fmulero deleted the dist-check branch October 27, 2022 14:19
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

Successfully merging this pull request may close these issues.

None yet

4 participants