Skip to content

Conversation

@hanthor
Copy link
Member

@hanthor hanthor commented May 27, 2025

This will allow maintainers to test if PRs are building successfully before merging

@alexiri
Copy link
Member

alexiri commented May 27, 2025

Some commits from #19 have leaked into this PR.

Copy link
Contributor

@imbev imbev left a comment

Choose a reason for hiding this comment

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

Ready after #19 is merged

@hanthor hanthor closed this May 29, 2025
@hanthor hanthor force-pushed the PR-build-checks branch from d2fd729 to ecce8e0 Compare May 29, 2025 07:14
@hanthor hanthor reopened this May 29, 2025
@yuravk
Copy link
Contributor

yuravk commented May 29, 2025

I don't think it is useful to run for each push as well.
PRs seem enough for me.

@hanthor
Copy link
Member Author

hanthor commented May 29, 2025

@yuravk removed the push

@alexiri
Copy link
Member

alexiri commented May 29, 2025

I think this will also update the latest, 10 , etc. tags for builds from a PR, which is certainly not what you want.

@hanthor
Copy link
Member Author

hanthor commented May 29, 2025

I can change it to not push when its a pull_request

@yuravk
Copy link
Contributor

yuravk commented May 29, 2025

I can change it to not push when its a pull_request

Yes, it is better to not push to registries, but just build.

@hanthor
Copy link
Member Author

hanthor commented May 29, 2025

Fixed

@alexiri
Copy link
Member

alexiri commented May 29, 2025

I think build.yml also needs some ifs to not run push-manifest.

@hanthor hanthor marked this pull request as draft May 30, 2025 01:57
if: ${{ env.res != 0 || github.event_name == 'workflow_dispatch' }}
shell: bash
run: sudo podman run --rm -ti ${{ env.IMAGE_NAME }} bootc --version
run: sudo podman run --rm -ti ${{ env.IMAGE_NAME }} bootc container lint --fatal-warnings
Copy link
Member Author

Choose a reason for hiding this comment

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

I'm unsure about the use of --fatal-warnings if it will cause things to fail that should pass.

Copy link
Contributor

Choose a reason for hiding this comment

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

The Containerfiles already contain linting, so that can be removed here or there.

Our disregard of the lint warnings hasn't caused major problems yet, so I think we can keep it non-fatal for now. Eventually it may be useful to enable the fatal warnings.

@hanthor hanthor marked this pull request as ready for review May 31, 2025 10:05
@kfox1111
Copy link

Heh. Was starting to re-implement this as I needed it, and didn't realize someone had started it already. Could we get this merged soon please?

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.

5 participants