# pijul-conflicts
List known conflicts in the current channel without touching the
current working copy.
## Quick spin
Build with `cargo build` and run `test.sh` from the root of the
folder. It'll create a repository in a temporary directory, make some
changes to produce a conflict, then print it.
## Caveats
In a helpful message from Pierre-Étienne Meunier (the author of Pijul)
on Zulip
([here](https://pijul.zulipchat.com/#narrow/stream/270693-general/topic/Pijul.20status/near/365680209)),
it was pointed out that this implementation will run in the time
linear in the size of the repo which could be an issue for large
repositories.
## TODO
 - Structure tests better?
 - Figure out ways to produce, detect and print the different kinds of
   conflicts -
   [libpijul::output](https://nest.pijul.com/pijul/pijul:main/SXEYMYF7P4RZM.H5AAU)
   lists the different kinds of conflicts that can be returned