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.

Sign up for GitHub

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

Jump to bottom

fix: use correct syntax for no-lockfile option #203

Merged
merged 1 commit into from
Sep 19, 2023
Merged

fix: use correct syntax for no-lockfile option #203

merged 1 commit into from
Sep 19, 2023

Conversation

nicolasgasco
Copy link
Contributor

@nicolasgasco nicolasgasco commented Sep 19, 2023 •
edited
Loading

This PR is a sort of a follow up to this other PR: #202

In this PR I am using the correct syntax for the no-lockfile option. Sorry for the confusion.

@nicolasgasco nicolasgasco self-assigned this Sep 19, 2023
vscav
vscav approved these changes Sep 19, 2023
View reviewed changes
Copy link
Member

@vscav vscav left a comment

Choose a reason for hiding this comment

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

Thanks @nicolasgasco 🙏

@vscav vscav added the internal label Sep 19, 2023
@nicolasgasco nicolasgasco merged commit 743ff11 into main Sep 19, 2023
10 checks passed
@vscav vscav changed the title Use correct syntax for no-lockfile option fix: use correct syntax for no-lockfile option Nov 17, 2023
@michelegera michelegera deleted the fix-no-lockfile branch December 28, 2023 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@vscav vscav vscav approved these changes

Assignees

@nicolasgasco nicolasgasco

Labels
internal
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@nicolasgasco @vscav