-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add lock creation date to 'git lfs locks' output #4109
base: main
Are you sure you want to change the base?
Conversation
CI failure isn't caused by changes in this PR. |
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.
This seems like a fine change. Could we get some integration tests for it?
Also, I think we've fixed the CI problem, so if you rebase on master
when you add the tests, I think that should pick up the fix.
Before doing that, I have a question: is there any way to list locks in machine-friendly format? If no, people might parse output of |
There is a |
60a1f7b
to
020260c
Compare
020260c
to
aa82d8b
Compare
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.
Yeah, this looks good.
Could we get some integration tests (maybe in t-locks.sh
)? I realize that we may need to perform regex-based matching, which is fine, but I'd like to make sure we don't regress things.
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.
Hola mundo soy Max,sugerencia de refuerzo de seguridad.
No description provided.