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

remove reference to unused verification from github workflows #4296

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

deitch
Copy link
Contributor

@deitch deitch commented Sep 26, 2024

A prior commit removed the separate verification image and integrated it into installer. This removes a call to that make target from the publish.yml workflow, and updates the CODEOWNERS to reference the correct ones.

A prior commit removed the separate verification image and integrated it into installer. This removes a call to that make target from the publish.yml workflow, and updates the CODEOWNERS to reference the correct ones.

Signed-off-by: Avi Deitcher <avi@deitcher.net>
Copy link
Member

@OhmSpectator OhmSpectator left a comment

Choose a reason for hiding this comment

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

Look good.
I'm just thinking that at some point, we should start backporting changes in GitHub workflows to the LTS branches to avoid difficulties with PR handling targeting them.

Copy link
Member

@uncleDecart uncleDecart left a comment

Choose a reason for hiding this comment

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

LGTM, +1 on stable backport of GHA

@deitch
Copy link
Contributor Author

deitch commented Sep 26, 2024

I have been wondering about that. Should our workflows be subject to dealing with branches and backports? Or should we have perhaps a separate repo - or branch - dedicated solely to workflows, which the other branches all just reference?

@deitch deitch merged commit 8822a92 into lf-edge:master Sep 26, 2024
18 checks passed
@deitch deitch deleted the remove-unused-verification branch September 26, 2024 09:04
@OhmSpectator
Copy link
Member

@deitch. @uncleDecart I think right now we have the only solution of backporting to the -stable branches. Later, we can think about how to make it easier. Read about the best practices, etc...

@OhmSpectator
Copy link
Member

@deitch @uncleDecart I created an issue to track it: #4297

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.

3 participants