@6543 merged current
could you add some tests?
currently don't have the time. also, from the PR head:
I didn't add tests because it would effectively just test gitea's API to…
never mind, this breaks the default values for me after futher testing:
I still don't get the exact context where this helps, but it doesn't seem to break anything :)
I can't observe a difference in behaviour. Again, can you clarify what case is better handled with this?
Without fetching the issue by index and the repo settings, tea can't know what to do.
We can of course add that, but it will make
tea o <idx> non-instantaneous
:D I'd leave that out, @foo/bar clearly identifies this as a team already.
Can you describe which case is enhanced with this?
This might give wrong / ambiguous results:
Did you test what happens when you pass a sha to
TeaFindBranchRemote() that is on multiple…
I think the output flag needs to have
json added as well
One nit, otherwise LGTM