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

👷 ci: Verify lockfile in case commit-lockfile is false #1011

Merged
merged 4 commits into from
Dec 19, 2024

Conversation

LogFlames
Copy link
Member

@LogFlames LogFlames commented Dec 11, 2024

In case commit-lockfile is false it will verify the lockfile instead of commiting a new one. Previously if you set commit-lockfile and only wanted it to check the lockfile, in case the pom.xml had updated. It would create the new lockfile, not commit it, and then successfully finish the action.

It now allways runs the verify in case commit-lockfile is false, if commit-lockfile is true it will verify if pom is same and update/commit if pom has changed.

Added documentation in the README.md for the action parameters.

@LogFlames LogFlames linked an issue Dec 11, 2024 that may be closed by this pull request
@LogFlames LogFlames force-pushed the 880-github-action-doesnt-fail-on-invalid-lockfile branch 2 times, most recently from 16e668f to bfc8af4 Compare December 17, 2024 16:12
@LogFlames LogFlames force-pushed the 880-github-action-doesnt-fail-on-invalid-lockfile branch from bfc8af4 to d4032a2 Compare December 19, 2024 16:38
@LogFlames LogFlames merged commit b497f77 into main Dec 19, 2024
9 checks passed
@LogFlames LogFlames deleted the 880-github-action-doesnt-fail-on-invalid-lockfile branch December 19, 2024 16:51
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.

Github Action: Doesn't fail on invalid lockfile
1 participant