v0.14.5

Added

• Tasks has Sync beside Report. It records a merge the pull request already has, then writes the Customer report from that trace, including a deploy made with git shuttle deploy when that merge is in what was deployed.

v0.14.4

Fixed

• The side panel no longer slides sideways when a deploy lists a long module line or a long server name. The modules wrap in the field.
• A wrong deploy field and a wrong settings value say so under that field. The panel no longer clips the focus ring to stop the sideways slide.
• Field outlines meet the contrast of a control, and the small labels share one size. On a narrow window the fields stay large enough that a phone does not zoom in.

v0.14.3

Changed

• Dialog lists share one row: what the item is, its actions, then a note that wraps. A detail is the same label-and-value grid in a card, a trace, and Deploy.
• Menus, branch lists, and selects use the same padding and the same quiet status text. A finished command stays quiet; a warning and a failure stay marked.

v0.14.2

Changed

• A known value is quiet text in the field, using the same word as the list (remote, local, local + remote, in use), instead of a green "exists" line. A missing name is still a warning.
• The Prod column is shown only when a commit is not in production yet. Pull stays the primary action. A finished stage, an installed add-on, and a command that succeeded are quiet text; a warning, work in progress, and a failure keep their colour.

v0.14.1

Fixed

• A release made by naming commits (the Release tab) is recorded on the task those commits belong to. The customer report then shows that release, and a later deploy of the release line that contains the release branch, including a cherry-pick that was already made.

v0.14.0

Changed

• The Customer report of a task no longer needs a pull request. After git shuttle merge (and ship) of a branch that is for a task, whose add-on has
  the report turned on, git shuttle shows the steps of the task from its trace (started, commits, pushed, merged) and asks, the same way as after
  git shuttle pr; a pull request that exists is added to them. git shuttle trace report works for a branch without a pull request when the trace
  has steps of the task (it said "there is no pull request" before); without a pull request and without a step it says so.

v0.13.1

Fixed

• git shuttle trace bind took a new branch for a merged one: a branch made at the tip of the base, which is the merge of somebody else's pull request,
  was given that merge and the commits of the other person, and they showed under its task in the graph and the Release tab. A branch with no commit
  of its own is now taken for a merged branch only when the merge names it ("Merge branch 'x'", "Merge pull request #1 from owner/x").

v0.13.0

Added

• Where a commit is on its way to production: a new Prod column in the graph, and the same mark in the details of a commit. In prod is a commit
  that the release branch has, or has with the same patch under another hash (a cherry-pick); On its way is in a release branch whose pull request is
  not merged yet (the pointer says which); Not in prod is merged into the integration branch and nowhere else. Other commits say nothing. The search
  box of the graph finds them by those words. The answer of GET /repos/<id>/release-state is read-only and kept until a branch moves.

Changed

• The Release tab: the choice between the commits not released and all of them is two buttons with their counts (it was a check box), every commit
  is in the same columns (box, id, task, message, author), and with All each commit says where it is, with the same mark as the graph. The search
  finds a commit by its author too. A merge says how many of its commits are not released yet.
• The API level is 13: the page needs release-state; an older server says so.

v0.12.0

Changed

• The task picker (Start tab, Tasks dialog): every filter has a caption (Stage, Project, Fetched, Order); each task is two lines (number, title and pills, then its project and fetch state); the stage is coloured by what it says (done, waiting, running); the list scrolls by itself and no longer passes the scroll on to the panel.
• When the add-on does not answer (Odoo is slow or off), the picker shows a warning with a Try again button instead of a grey line.
• The task filter of the toolbar is marked when it is on (a teal frame) and has a button to clear it.

Fixed

• The browser tests no longer see an add-on that is installed on the machine (git-shuttle-odoo-task) next to the stand-in they use.

v0.11.3

Fixed

• The trace of a task shows the deploy of its release branch: a release branch holds cherry-picks (other hashes), so the merge of the task was never in what was deployed to production. A deploy of the release branch of the task, after its release, is now part of its trace.

Changed

• The Customer Report names a deploy of a branch with release in its name Deployed to prod; the other deploys stay Deployed.