Unique exit codes about cli

[dwbit]

Thanks again for the feedback. We're responding to and reviewing all stale label comments. As the moderator for the forums, I'll share any existing discussions/feature request links in closed Github issues if available. Feature Requests are tied to user accounts on the forums, and anyone in this thread is welcome to continue the conversation there by creating one.

[bitwarden-bot]

Hi seanfarley,
We're cleaning up our repositories in preparation for a major reorganization. Issues from last year will be marked as stale and closed after two weeks. If you still need help, comment to let us know and we'll look into it.
Thanks!

[tukusejssirs]

Was this issues fixed? I think that Bitwarden CLI should definitely use unique exit codes per error.

[dancorne]

Please don't close! It'd be useful for scripting to know if bw is returning an error due to not being logged in, unlocked, or not finding an item.

[dwbit]

Hey everyone, since this is a request, we'll be moving the discussion over to the Bitwarden Community Forums and closing the issue. There isn't currently a post in the Feature Requests category for this functionality, so you are welcome to create one.

[tukusejssirs]

@dwbit, why don’t you simply move the open issues to BCF instead of simply closing the issues? Closing the issues won’t solve them.

[dwbit]

Thanks for the feedback @tukusejssirs. Since this request is from 2018, the best way to move forward is to fascinate further discussion, and the best place for that is the forums. Anyone is free to create a post to kick-off the chat.

[tukusejssirs]

Well, I’ve been notified (by @bitwarden-bot) of about 4 other issues that they are labelled ~stale. What about moving these issues directly to the forum and the moderators sort the issues out there?