Points to cover:

• playbook for how to get started with testing
• differences between testing locally vs staging vs production
• how to configure tests for different environments

@johngrimsey thank you for the idea! Please feel free to comment if I missed something.

In each of the top level commands - az boards, az pipelines, az repos, az artifacts and az devops, we include the line indicating that this command is a part of azure-devops extension. In addition to this, we need to include the link out to the documentation - https://docs.microsoft.com/en-us/azure/devops/cli/?view=azure-devops as well.

Azure/azure-cli-extensions#1454

Need better docs (or more easier to find docs) for contributing (e.g. coding standards, etc). The snippets contributor guide is currently buried under snippets ... consider elevating it to the root and generalizing it to apply to all samples.

There are several places within the instructions whereby the instructions/screenshots are not reflective of the steps which must be done. This lab needs updating ASAP as in its current state it is just unnecessarily confusing!

It would be apt to include in the documentation the difference between this project (Terracognita) and its alternatives - Terraforming and Terraformer. It would be great if you can expand on what you said in this [Reddit comment](https://www.reddit.com/r/Terraform/comments/c4jhy7/cycloid_opensource_terra

I suggest using plaster to scaffold all files needed for new cmdlets

https://github.com/PowerShell/Plaster/blob/master/

I suggest the following things to scaffold from templates:

• cmdlet file with name Verb-VSteamAction
• create markdown docs with synopsis file and basic doc file
• check whether during scaffold we can already define parameters for the cmdlet and also add it to the files

If we have no branch and git-link-use-commit is nil we'll get an empty path segment, e.g., path//foo. Under these circumstances we should should signal a "cannot figure out what to link to" error and not return a link.

Due to the complexity of the setup, ingress support in draft was removed in favour of draft connect (see Azure/draft#573). In 0.12.0 and above, it's recommended in the documentation to use draft connect as it initiates a tunnel straight to all the pods without needing to set up ingress controllers, DNS, etc. Are there plans to eventually migrate over, or are there limitations with the current

Describe the bug
When Safari browser is used to print diagrams (PNG/JPG etc), it has a black background.

To Reproduce
Steps to reproduce the behavior:

1. Print or export any diagram while using safari browser on MacOS.
2. The printed/exported diagram will unexpectedly have a black background.

Expected behavior

1. No black background in the diagram.

Screenshots
TBD

Would it be possible somehow to use the vscode-powertools to "pin" certain files, so that they won't close with cmd+w (on mac)?

I'm thinking to remap cmd+w to a powertool somehow, and make it call the vscode default close action, but first compare the file path with a simple list of files (".vscode-pinned-files") to see if the files are there. I can make a safe-to-close.sh shell script myse

If there is any inline image of description with file name like "screen shot.jpg" are not mapping. So I fixed it like this in Agent.cs class. As the images is getting saved as "screen+shot.jpg" when Jira son is exported

private void CorrectImagePath(WorkItem wi, WiItem wiItem, WiRevision rev, ref string textField, ref bool isUpdated)
{
foreach (var att in wiItem.Revisions

It appears like Visual Studio 2019 with SARIF viewer extension is not working quite well.

• Visual Studio is expecting the version attribute to be at the top! When we do to_json(sarif schema) the attributes are getting sorted alphabetically so the runs attribute is on the top and version is at the bottom. We need to find a workaround for this
• Our url encode is encoding and converting the

Feature description

$ git credential-manager-core --help
No manual entry for git-credential-manager-core

Either a real man page or at least link to the online documentation.

I'm trying to set up a new instance of Aggregator CLI as an Azure function app. I've created the app on Azure and think I've installed Aggregator CLI, but don't know how to save my Azure DevOps (VSTS) Personal Access Token (PAT) to Aggregator in order for the app to authenticate against DevOps.

What I've done so far

1. Created a new resource group on Azure
2. Created a function app on Az

The APIs have hard dependencies on Cosmos DB API, which makes unit testing very difficult.
Perhaps we should do some refactoring and introduce a data access layer.

1. Create a personal access token with the authorized scope Agent Pools(read, manage) following these instructions. You will have to provide later the base64 encoded value of this token to the vstsToken value of the chart.

The instructions link is dead: 404 - Page not found

In [README.md](https://github.

Please add a confirmation dialog to the End Session to confirm or abort ending of session as this deletes the session.