Comment on a change

The Drought curve parameter in the right pane: its changed values, the parameter that uses it, the commit that changed it, and a reviewer's question on the August value with the modeller's answer, then the Reply and Resolve buttons.

Write in Comment on this component and send it. The modeller gets the comment as on any pull request, and answers it in VS Code or in the browser. Select Reply to answer a comment, and Resolve once its question is settled. Branch policies can stop a pull request from being completed while a comment is still active.

To propose another value, select Suggest a value under it, type the value and post it. The suggestion is a comment on the line of the value: the modeller sees the line with your value and can apply it from the Files tab of the pull request.

The Abstraction licence parameter, changed from 40 to 45, with a suggested change of its line to 42 and the reason: the 2026 permit allows 42 Ml/d.

Some changes, such as a removed edge, have no lines of their own in the new file. Comment on a node they connect to, or on the whole pull request.

Open comments on the whole pull request are listed at the top of the Changes pane, in Comments on the pull request. They include messages from bots, such as a request for a licence check. Select a comment to read it in the right pane, where you can reply to it or resolve it.

Post a summary of the changes, in the right pane when no change is selected, writes a comment that lists the model changes with their old and new values. It is for the people who read the pull request in Azure Repos or in the emails of Azure DevOps. Once posted, the button updates the same comment.

The summary comment: model.json has 3 changed parameters, listed in a table with their type, their change and their values, such as value.value from 40 to 45 for the Abstraction licence.

Pywr for VS Code and Pywr for Azure DevOps are developed and maintained by Stefano Simoncelli.