Allow use of docker/lint.sh clang_format with git-worktree

[areusch]

• mount repo at $(pwd) by default; fixes problems when using git-worktree.
• allows usage of docker/lint.sh with arbitrary tvm repo

cc @jroesch@mikepapadim@tqchen

[tqchen]

@areusch let us do a quick check in case some of the CI might depend on the /workspace behavior

[areusch]

@tqchen last time it was the rust rebuild which is conveniently disabled now :)

[areusch]

not that i am trying to actively break rust but i don't understand the build system enough to know how to fix it and last time the PR languished forever and died because no one was willing to help.

[leandron]

* mount repo at $(pwd) by default; fixes problems when using git-worktree.

What is the problem when using git-worktree? I'm not very familiar with it.

* allows usage of docker/lint.sh with arbitrary tvm repo

Maybe we could add a "usage" example in the header of the script, to instruct people on how to do that?

Also, a bit off topic for here but I think we really should think about processing the inputs in a loop so that users can provide non-positional parameters in any order.

[leandron]

It would be good to add this on line 23 small documentation to the command line, also to show the order in which parameters need to be provided.

[areusch]

done

[areusch]

@leandron try running docker/bash.sh ci_cpu git status from a git-worktree root that's not the original cloned repository. it will fail because it can't access the original repo (the original repo path is placed as a relative path in .git). by mounting the repo based on the pwd, this issue is worked around.

Maybe we could add a "usage" example in the header of the script, to instruct people on how to do that?

ack

Also, a bit off topic for here but I think we really should think about processing the inputs in a loop so that users can provide non-positional parameters in any order.

will see if i can do this in next patch

[areusch]

superseded by #8670