From a9167147b6a8777145a827e1d40b3738518bd89d Mon Sep 17 00:00:00 2001
From: Jonathan Creekmore <jonathan@thecreekmores.org>
Date: Mon, 13 Jan 2025 03:17:53 -0600
Subject: [PATCH] issues can now be closed as `duplicate` (#741)

Recently, GitHub added the ability to [explicitly close an issue as a
duplicate](https://github.blog/changelog/2024-12-12-github-issues-projects-close-issue-as-a-duplicate-rest-api-for-sub-issues-and-more/#close-an-issue-as-a-duplicate).
When you close an issue as a duplicate, in addition to linking it to the
issue and putting an event in the timeline, it _also_ sets the the issue
state reason to `duplicate`. I cannot find this behavior documented in
the current GitHub API docs, but I have seen it in the wild on a few
recent issues in the rust-analyzer repository.
---
 src/models/issues.rs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/models/issues.rs b/src/models/issues.rs
index a5a9f7c4..bfb9e290 100644
--- a/src/models/issues.rs
+++ b/src/models/issues.rs
@@ -71,6 +71,7 @@ pub enum IssueStateReason {
     Completed,
     NotPlanned,
     Reopened,
+    Duplicate,
 }
 
 #[derive(Debug, Clone, PartialEq, Serialize, Deserialize)]