-
Notifications
You must be signed in to change notification settings - Fork 9
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
chore: verify lockfile on PR, commit on push to main #877
Merged
LogFlames
merged 14 commits into
main
from
875-update-ci-so-that-it-works-for-pr-from-external-forks-contributors
Sep 11, 2024
Merged
Changes from 2 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
998ae53
verify lockfile on PR, commit on push to main
LogFlames 03f0484
consistant naming
LogFlames 786e2db
Separate lockfile verification/updating into separate actions for PRs…
LogFlames 7d0cfe7
Keep Lockfile name for doc generation during push to main
LogFlames 07d1d49
Always try to commit lockfile. In case of error the actions fails and…
LogFlames ad13bb8
uneccessary default argument
LogFlames 89901f7
Merge branch '875-update-ci-so-that-it-works-for-pr-from-external-for…
LogFlames e7d3825
verify lockfile on PR, commit on push to main
LogFlames 5755f6e
consistant naming
LogFlames 1c6a6d2
Separate lockfile verification/updating into separate actions for PRs…
LogFlames f17720a
Keep Lockfile name for doc generation during push to main
LogFlames ed8dc56
Always try to commit lockfile. In case of error the actions fails and…
LogFlames 6b88db8
uneccessary default argument
LogFlames 49de491
Merge branch '875-update-ci-so-that-it-works-for-pr-from-external-for…
LogFlames File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 think we should remove "pull_request" here
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.
Should we separate it into two workflows, one that commits a new lockfile on push to main, and one that verifies that the PR has a correct lockfile (and could commit a new one to the source branch if the PR is this repo).
We then technically do it twice and the one that runs on pushes to main would be a safety if something would get merged without an updated lockfile.
Or skip validation of the lockfile on PRs and simply update it on every push to main?
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.
yes, completely, that would be much cleaner. and the modification one would be removed once renovate will be able to update both the pom and the lockfile at the same time.