287 — tp overview colours a repository by its Peacock colour (#287)

Why

The board (#279) gives each repository a colour of its own so that a card's project can be told at a glance, but the colour is made up: it follows from where the repository's name falls among the others on the page, means nothing, and moves when a repository joins or leaves. Each project already has a colour its owner chose and sees every day: its Peacock colour, which tints its VSCodium window. A card in that colour is recognised without reading the name.

What changes

  • tp overview: a repository's cards take its Peacock colour, the peacock.color of .vscode/settings.json on the repository's default branch on the forge. A repository that sets none, or whose setting is not a colour, keeps the generated colour of #279.
  • The colour is the committed one: a Peacock colour changed in an editor and not yet on the default branch is not seen.
  • docs/overview.md.

Acceptance

The colour of a level 3 repository's cards, the same in every column. "Generated" is the colour #279 gives.

.vscode/settings.json on the default branch peacock.color in it The cards' colour
absent — generated
present not set generated
present "#11ddaa" #11ddaa
present "#2cb" #2cb
present, with comments and trailing commas, as VSCodium allows "#eebb11" #eebb11
present set only in a commented-out line generated
present not a hex colour: "red", or "#12; x" generated
cannot be read: the forge answering an error — generated; the repository's cards still shown, and no notice
Repositories on the board Outcome
one with a Peacock colour, one without the first in its Peacock colour, the second generated
two with the same Peacock colour both in it
two without different generated colours, as #279

Out of scope

  • The colour of a local checkout's VSCodium window where it differs from the committed one, and reading any checkout.
  • A colour set in the user config, or in task-plus.yml.
  • Keeping generated colours apart from the Peacock ones on the page.
  • A legend of repositories and colours.

Decisions

none

Done when

  • tests express the acceptance table and pass
  • spec updated
  • ADR written if a fork was resolved
  • changelog entry
  • issue closed with a link to the release