<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Collaborate/take over this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=353137) </details> <!--IssueSummary end--> ## Problem to Solve The [`/merge_requests`](https://docs.gitlab.com/api/merge_requests/#list-merge-requests) API currently returns all merge requests, even when the merge requests are in a read-only project that has been archived. This makes it challenging to see merge requests that you actually need to do anything with via the API since archived projects likely don't need any action. ## Proposal In the `/merge_requests` API a new field should be added which is `non_archived` (to match the currently available field in the groups API). This field should be **Defaulted to `false`** so as not to introduce a breaking change. <details> <summary> Old Description</summary> `non_archived` is an optional parameter to the [group-based MR API](https://docs.gitlab.com/ee/api/merge_requests.html#list-group-merge-requests) this does not appear to be supported for other MR APIs (scoped by project or user) first observed this when querying for open merge requests and finding MRs that are in archived projects. these are particularly annoying because you can't close them without unarchiving the project. adding `non_archived` to any MR-based operation (and having it default to `true`) would be a better experience. it would also be more consistent with the issues API which seems to honor this field in multiple APIs </details>