Martin Peck

> Seems to me it's more an issue with Azure CLI itself than with azbrowse. Could be, but I spend most of my day using `az` without issue.

I'm on MacOS (Ventura now, but the original bug would have been on a previous release) I'm using iTerm2, zsh, and have latest az.

Is there a way I could "trick" `azbrowse` into thinking it always needed to do an update? i.e. can I force azbrowse into the upgrade path so I can repeatedly...

Creating labels: https://developer.github.com/v3/issues/labels/#create-a-label Patching labels: https://developer.github.com/v3/issues/labels/#update-a-label

https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning

Can you explain why you've tagged me in this issue please? Beyond fixing a 1 character typo in the README, I wouldn't consider myself as someone to tag on issues...

What was the reason for the force-push?

You've removed quite a few try/except blocks. This might be fine, but it's not mentioned in the PR notes, and I wasn't sure if this change was desired/expected. Probably best...

Alternatively, don't run builds that require secrets against PRs. Only run them against branches, once merged