dev.knotless.state

Kept in the account of whoever changed it. Readers take the latest from someone allowed to make it: the subject's author, the repository's owner or a collaborator; `merged` only from the latter two; for a thread, also the pull's author.

Details · record, key tid
Kindrecord
Record keytid
Authorityknotless.dev
Indexed

Record

record · key tid

Properties

base

string

For a pull, the branch it targets from here on, without refs/heads/: set when the branch it targeted was renamed, or went as the pull with that head branch landed.

  • maxLength: 255

batch

string

For `merged` by a merge queue, the hex object ID of the tip of the batch it landed in: the commit whose checks let it land. The pulls merged with the same `batch` were checked and landed together.

  • minLength: 40
  • maxLength: 64

commit

string

The hex object ID of the merge commit, for `merged`.

  • minLength: 40
  • maxLength: 64

createdAt

requiredstring · datetime

from

string

For `merged`, the hex object ID the base was at before the merge: from..commit is what the pull brought in, whose commits readers may then show as its author's.

  • minLength: 40
  • maxLength: 64

pull

string · at-uri

For `closed` on an issue, the dev.knotless.pull whose merge closed it, as its title or body named the issue after a closing keyword such as `Fixes`. Beside `since`, the pull a pull was moved off as it landed.

repo

requiredref

The repository the pull or issue is on.

since

string

Beside `base`, for a pull moved there as the pull it was built on landed: that pull's head, the hex object ID its own changes start from.

  • minLength: 40
  • maxLength: 64

state

string

`merged` applies to pulls only; `resolved` and `open`, to a thread. Absent when the record only sets `base`: the state stands.

  • maxLength: 64
  • knownValues: open | closed | merged | resolved

subject

requiredstring · at-uri

The dev.knotless.pull or dev.knotless.issue whose state changed; or the dev.knotless.comment, with a `line`, that starts a thread.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • A pull or an issue, and everything said on it.

  • A pull set to merge by itself once its checks pass, or that setting cancelled.

  • A pull put in the merge queue of the branch it targets, taken out of it, or turned away by the runner that lands the queue.

  • A request to merge a branch into a repository, kept in the requester's account.

  • Closes or reopens a pull or an issue, or resolves a thread on a pull's lines or opens it again, as the account logged in to this appview's pages.