isidentical opened a new issue, #3744:
URL: https://github.com/apache/arrow-datafusion/issues/3744

   **Is your feature request related to a problem or challenge? Please describe 
what you are trying to do.**
   Since the only `Cargo.lock` that is checked in is the `datafusion-cli`'s 
one, we seem to be forgetting about updating [it 
sometimes](https://github.com/apache/arrow-datafusion/pulls?q=is%3Apr+Cargo.lock+is%3Aclosed).
   
   **Describe the solution you'd like**
   Since we already have infrastructure (a lint job), I think it should be 
relatively simple to add a step that checks whether the `Cargo.lock` is 
up-to-date or not. It could then fail on PRs that change `Cargo.toml` (add new 
stuff to other crates), and let the PR authors know that they need to update 
the lock as well.
   
   **Describe alternatives you've considered**
   Leaving as is.
   
   **Additional context**
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to