# "dvc status --diff"

**URL:** <https://discuss.dvc.org/t/dvc-status-diff/1855>\
**Category:** Feature Requests\
**Created:** [November 28, 2023, 1:54am UTC](https://discuss.dvc.org/t/dvc-status-diff/1855 "2023-11-28T01:54:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregstarr](https://avatars.discourse-cdn.com/v4/letter/g/c77e96/32.png) [@gregstarr](https://discuss.dvc.org/u/gregstarr)\
**Post date:** [November 28, 2023, 1:54am UTC](https://discuss.dvc.org/t/dvc-status-diff/1855/1 "2023-11-28T01:54:57Z")

</div>

One thing that happens to me a lot is that I will call `dvc status` and it reports that one of my code dependencies changed and I don’t remember what specifically I changed. It would be great if there was an option for `dvc status` to do a git-like diff on the code files so you can easily check if your changes have an impact on the stage.

---

<div class="post-metadata">

**Author:** ![kupruser](https://avatars.discourse-cdn.com/v4/letter/k/e95f7d/32.png) [@kupruser](https://discuss.dvc.org/u/kupruser)\
**Post date:** [November 28, 2023, 8:56pm UTC](https://discuss.dvc.org/t/dvc-status-diff/1855/2 "2023-11-28T20:56:41Z")

</div>

Unfortunately, dvc doesn’t really track the contents of code dependencies (one could argue if it should) to be able to show git-like diff for them, so the best we could do would probably be just wrapping `git diff`, at which point I’m not sure how useful it would really be.