Skip to content

Prices and changes

Markdown

Some facts on a page keep changing after you save it: a product’s price and availability, a package’s version, an issue’s state. Copilka checks those again from time to time and keeps the history.

  • Prices and availability, on anything with a shown price: products, books with a price, listings, events with tickets.
  • Versions, on packages.
  • State, on issues and pull requests: open, closed, merged.
  • Anything in a room with a rule that closes a status by itself; see Properties.

Only changes are recorded, so the history is a list of moments the fact moved, up to a hundred for prices.

Settings → Reading → Check prices: Anything with a watched fact — a price, a version, a state — is read again this often. Never, Daily (the default) or Weekly. The checks run when Copilka launches and through the day while it is open, a couple of dozen items at a time, oldest first. Nothing runs while Copilka is closed.

A re-check is a fresh reading of the page, so in a room with properties the reader fills in, it also fills those again.

  • On the card, the price tag carries an arrow when the price has moved, with the amount it moved by.
  • A card whose watched fact changed shows a badge with the old value struck through: 1.4.2 → 1.5.0.
  • In the details panel, a price has a small chart of its history and a line such as Down from £45, saved 12 September.

Appearance → Show prices on cards turns the tag and the badge off: The price tag, and the badge when one has moved. Events never show a price tag.

Price and change histories are kept on the Mac that recorded them and are not synced.