You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine if I have a long list of contributors or I don't want to set the same default reviewers all the time but I also don't want to type their emails out when declaring the reviewers.
An idea is to allow the user to define a list of contributors on the doing-cli config file, so a keyword (like the first name of the contributor) and its email address:
Would allow you to use the aliases in both reviewers and assignees:
doing create pr --reviewers 'john jane'. it needs a string because --reviewers takes a single option. doing would expand the string to 'john.doe@email.netjane.doe@webmail.org' before passing it to the az devops cli.
doing create issue "an issue" -a john
It would have to work with default_reviewers as well.
Thoughts? And, do you want to work on the PR or shall I pick it up? :)
Your idea sounds good to me.
We can scan the string of reviewers and if the individual elements don't include an @ in them, then we search for matches in .doing-cli-config.yaml#aliases. I like that :)
I don't think I'll be able to work on this for the next couple of weeks, though, so if you want to go ahead, that's fine with me :)
Imagine if I have a long list of contributors or I don't want to set the same default reviewers all the time but I also don't want to type their emails out when declaring the reviewers.
An idea is to allow the user to define a list of contributors on the doing-cli config file, so a keyword (like the first name of the contributor) and its email address:
So then I could do
doing create pr --reviewers john jane
What do you think? Does it sound useful?
The text was updated successfully, but these errors were encountered: