pub struct GitHubProjectItem {Show 23 fields
pub id: String,
pub kind: String,
pub title: String,
pub content_id: Option<String>,
pub number: Option<i64>,
pub url: Option<String>,
pub repository: Option<String>,
pub state: Option<String>,
pub state_reason: Option<String>,
pub body: Option<String>,
pub author: Option<GitHubUser>,
pub assignees: Vec<GitHubUser>,
pub labels: Vec<GitHubLabel>,
pub milestone: Option<String>,
pub comment_count: i64,
pub created_at: Option<String>,
pub closed_at: Option<String>,
pub is_draft: bool,
pub merged: bool,
pub review_decision: Option<String>,
pub archived: bool,
pub field_values: BTreeMap<String, GitHubProjectValue>,
pub updated_at: String,
}Expand description
One card.
Fields§
§id: String§kind: StringISSUE | PULL_REQUEST | DRAFT_ISSUE | REDACTED.
title: String§content_id: Option<String>What the card POINTS AT — the issue, the pull request, or the draft itself. Distinct from the card’s own id: a draft is edited by its content id and moved by its item id, and using one for the other is an error GitHub reports as “could not resolve to a node”.
number: Option<i64>The issue or pull request number, absent for a draft item — a draft lives only on the board and has nothing to open.
url: Option<String>§repository: Option<String>owner/repo, absent for a draft item.
state: Option<String>OPEN | CLOSED | MERGED, absent for a draft.
state_reason: Option<String>Why it is closed, when GitHub says: COMPLETED | NOT_PLANNED. The
difference between finished and abandoned is not something a board
should make a person open GitHub to learn.
body: Option<String>The description, as markdown. A draft card’s body is the whole of it — there is nowhere else to read it.
assignees: Vec<GitHubUser>§labels: Vec<GitHubLabel>§milestone: Option<String>§comment_count: i64How many comments the conversation has. The comments themselves are read from the repository’s own mirror when a card is opened — one mirror per conversation, not one per board.
created_at: Option<String>§closed_at: Option<String>§is_draft: boolWhether the pull request is a draft, and whether it was merged. Absent state on a merged PR reads as “closed”, which loses the distinction that matters most about a pull request.
merged: bool§review_decision: Option<String>APPROVED | CHANGES_REQUESTED | REVIEW_REQUIRED, for a pull
request that has been looked at.
archived: boolArchived on the board. An archived card is still an item and still has its field values; it is simply not shown unless it is asked for.
field_values: BTreeMap<String, GitHubProjectValue>Every field value this item carries, by FIELD id. Single-select values are the option id, so a column change is a value change and the page never has to match on names.
updated_at: String