2.5.0

Added

• A Hide closed checkbox in the kanban toolbar takes every closed sub-issue off the board, whatever the columns are made of. The choice is remembered like the other board settings.

2.4.2

Changed

• The age badge reads today, this week or this month for an issue younger than the chosen unit, instead of 0d, <1w and <1 mo.

2.4.1

Changed

• Kanban: an issue that had been closed as not planned is closed as not planned again when its card is dragged back to the Closed column, instead of always as completed.
• Kanban: the note saying when cards can be dragged sits in the toolbar rather than as a tooltip over the whole board, the List and Kanban buttons announce which one is pressed, and the filter value select has a name for screen readers.
• Kanban: a GitHub deployment that does not know the option list of single-select fields is asked again after ten minutes, and only that exact schema error triggers the plainer query, so column order and dragging are never switched off for good by an unrelated error.
• Kanban: sub-issue lists of epics visited more than five minutes ago are dropped from memory when a fresh one is loaded.
• Issue sidebar: the layout of the issue page is measured once per page and after a resize rather than on every scan.

2.4.0

Added

• Epic kanban: a List and Kanban toggle above the sub-issues list of an issue draws those sub-issues as a board. The columns come from any field the sub-issues carry, or from their state, type or assignee, and follow the order the organization gave a single-select field's options; the cards inside a column are ordered by the field, number, creation date, title, state, type or assignee you pick, in either direction. Both choices and the toggle are remembered. The board reads up to 500 sub-issues. On by default, one checkbox in the settings turns it off.
• Issue sidebar toggle: a chevron in the gutter between an issue and its metadata column hides that column, assignees, labels, type, fields, projects and the rest, leaving the width to the issue body and the board. The button keeps its place either way, the choice holds on every issue and in every tab, and it is not shown on a narrow window where GitHub stacks the sidebar anyway. On by default, one checkbox in the settings turns it off.
• Kanban filter: one value of any of those same dimensions keeps only the matching sub-issues, and the toolbar count says how many of the epic are left. Filtering happens in the page, without another request.
• Kanban drag and drop: a card dragged to another column writes the new value to GitHub when the columns come from a single-select field (createIssueFieldValue, or deleteIssueFieldValue for the "No field" column) or from the issue state (closeIssue, reopenIssue). The card moves first and returns to its column with the reason in the toolbar if the write fails, columns made of types or assignees are not drop targets, and a second checkbox in the settings turns dragging off. This is the only part of the board that writes, and it needs a token with write access.

2.3.1

Changed

• The added and removed line counts in the pull request size badge use the regular weight instead of bold.

2.3.0

Added

• Age threshold: the age badge turns yellow once an issue has been open longer than a number of days set on the Issue age card, 90 by default; 0 turns the highlight off. The hover text says when the threshold is exceeded.
• A badge reference on the site and in the README showing every badge and what its colour means.

Changed

• The pull request size badge shows added lines in green and removed lines in red, like GitHub's own diff counters.

2.2.1

Changed

• Badges are back to GitHub's outlined field-chip style, coloured text on a tinted background, so they stay visually distinct from labels. The solid style introduced in 2.2.0 is gone.

2.2.0

Added

• Pull request badges on Projects views: table rows and board cards whose item is a pull request get the same author, fork, size and merge state badges as the pull request list.

Changed

• Badges are solid pills like GitHub's labels instead of outlined, tinted chips, so they sit naturally among labels on pull request lists and project cards.
• The first option on the Pull requests settings card is shorter; the possible values are documented on the site and in the README.

2.1.0

Added

• Pull request badges on the pull request list, among the labels of each row. On by default: the author's relation to the repository (First-time contributor, First PR on GitHub, External, Contributor, Collaborator, Member, or Bot for apps). Optional, each with its own checkbox on the new Pull requests settings card: From fork, size as added and removed lines with the changed file count on hover, and merge state (Mergeable, Behind base, Blocked, Conflicts, Checks failing).
• Documentation: a pull request list example on the site and in the README, and an FAQ entry explaining each badge.

Changed

• The manifest description and the site mention pull request badges.

2.0.6

Changed

• On a board grouped by a field, the badge carrying that field's value is skipped too, since the column header already says it.