Return sensible results for archived repositories

Open alerque opened this issue 4 years ago • 1 comments

I've recently done a big of housekeeping across half a dozen orgs using Gitlab and we are now faced with a bunch of archived projects. GitLab handles this pretty graciously, but now the trouble is glab goes right on operating on all repositories if nothing changed.

[ ] It would be nice if ⓐ the search and ⓑ future list commands (c.f. #958) had some sort of flag to exclude archived repositories from their results and...
[ ] If output that does include such repositories reflect their status somehow so that there is some indication they are archived. Archived repos are read only and hence...
[ ] Attempting operations on them such as creating issues should return a sensible error having checked their status somehow rather than just returning the 403 forbidden header.

Feb 23 '22 17:02 alerque

This issue has been automatically marked as stale because it has not had recent activity. We haven't had the time to address it yet, but we want to keep it open. This message is just a reminder for us to help triage issues.

Mar 26 '22 02:03 clemsbot