dvc: Repo(..., rev=smth) is counter-intuitive or broken

For example repo.add() will browse using currently existing .dvcignore files. repo.pull/push() will work against master not rev.

Should we hide it? Or handle all of that? Or implement everything not using non-default rev Repo objects?

• either fix or drop rev
• remove assert rev is None in dvc.api

[Suor]

I would say that we may break someone workflow if make Repo reread config for each branch 😃 Some older branch may have no remote config. And when it will have a different one it could be quite surprising for a user that his files are pushed to two different remotes.

[Suor]

@efiop .push()/pull() use brancher and brancher only uses self.tree, if no kwargs are passed. So it was not as I described, but still fishy.

Still the point stands - do we really need repos with non-default rev?