Repository navigation
ADO Lens 0.7.3 - #11
Merged
Merged
Conversation
… trace, history of a branch, clearer environment map
Fixes from a real question: "pull requests merged into staging after release X, with their work items and tags".
- `ado_pr` and `ado_pipeline` (reading: pull request lists and details, merged PRs, builds, deployments, artifacts) are
in every mode now, the Product Owner one too; creating and completing PRs and running pipelines stay for developers.
- `ado_changes` of a pull request, changeset or commit lists its work items with type, state and tags.
- `ado_trace` checks the release stages in parallel and skips deployments older than the change: it no longer runs
out of time on items with several pull requests.
- `ado_file path=/ repo=<r> history=true version=<branch>`: the history of a whole repository or folder on a branch,
with pull requests and work items. An environment name given as the branch ("sbx03") is turned into its branch.
- The environment map reads "UAT (sbx03) = branch staging" instead of "UAT (sbx03) [staging]".
- The server instructions name the tools for "what went into a branch or an environment".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes from a real question: "pull requests merged into staging after release X, with their work items and tags".
ado_prandado_pipeline(reading: pull request lists and details, merged PRs, builds, deployments, artifacts) arein every mode now, the Product Owner one too; creating and completing PRs and running pipelines stay for developers.
ado_changesof a pull request, changeset or commit lists its work items with type, state and tags.ado_tracechecks the release stages in parallel and skips deployments older than the change: it no longer runsout of time on items with several pull requests.
ado_file path=/ repo=<r> history=true version=<branch>: the history of a whole repository or folder on a branch,with pull requests and work items. An environment name given as the branch ("sbx03") is turned into its branch.