Currently we use the most recent commit from GitRekt.GitAgent.tree_entries_by_path/3 and use it in the table header. But sometimes this is wrong for example when moving/deleting tree entries:
Instead of extracting the most recent commit from the tree table, we should either
make a second GitRekt.GitAgent.tree_entry_by_path/3 call.
find a way to match most recent commit for the given path directly without having to rely on the available tree entries.
Currently we use the most recent commit from
GitRekt.GitAgent.tree_entries_by_path/3
and use it in the table header. But sometimes this is wrong for example when moving/deleting tree entries:Instead of extracting the most recent commit from the tree table, we should either
make a secondGitRekt.GitAgent.tree_entry_by_path/3
call.