As of PR #115 we started seeing warnings for clippy's missing_safety_doc lint. Unsafe functions should document what preconditions have to be met in order to safely call those functions.

Remove all instances of -A clippy::missing-safety-doc in .travis.yml (or whatever pipeline we're using by then) when resolved.

Expected Behavior

• overflow minimizes menu

Current Behavior

• the menu and headings overlap
• search background out of sync with boundaries

Possible Solution

According to the docs, the teamcity integration needs a "build configuration id". Since this is something attached to each project it doesn't make sense - I would assume that node-build-monitor is able to monitor all builds on a teamcity server and not just a single one? I've tried setting it to "*" but that didn't do anything. It would be great if configuration items were clarified (both in terms

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!

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

import os
from azure.devops.connection import Connection
from msrest.authentication import BasicAuthentication

Fill in with your personal access token and org URL

PERSONAL_ACCESS_TOKEN = os.getenv("PERSONAL_ACCESS_TOKEN")
ORGANIZATION_URL = 'xxxxxx'
PROJECT_NAME = "xxxxxx"

def create_pipeline_client():
# Get connection from devOps & create pipeline client
credentials = Basic

Support Netlify

Documentation: https://docs.netlify.com/configure-builds/environment-variables/#git-metadata

Environment variables:

• service detection: NETLIFY
• Branch: BRANCH
• Commit sha: COMMIT_REF
• Is Pull request: PULL_R

When running ./migration.exe init, there is a configuration.json generated.
There is a property named 'AttachmentMazSize' instead of 'AttachmentMaxSize. Z instead of X.

In the documentation there is this rollup sample:

It says: This aggregation will total the values found in the Estimated Dev Work and Estimated Test Work field

I didn't see anywhere one visualstudio.com to report this, so I'm doing it here. The ReadMe on this repo is 1000x clearer with what's going on. However, when looking for examples of how to create this type of extension for VSTS you find this tutorial. That tutorial needs updated to reflect the readme, reference it, or

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

This is useful as it allows the user stories to be dragged first on a new feature w/o having to drag the feature first

It is not possible to remove the target platform architecture to build arm and arm64 in one apk.
The list is missing an empty entry.

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.

Should use as a starting point:

• https://github.com/madskristensen/WebCompiler/blob/master/CONTRIBUTING.md
• https://github.com/code-cracker/code-cracker/blob/master/CONTRIBUTING.md

Besides that, should add:

• Coding Style
• Project Structure
• How to build
• Unit tests

Currently there is no output for chouts or <<< >>>.

I am using 'local_exec' in my terraform files. Like this

resource "azurerm_storage_account" "sa-main" {
        name                    = "ngh${var.deployment}maina"
        resource_group_name     = "${azurerm_resource_group.rg.name}"
        location                = "${azurerm_resource_group.rg.location}"
        account_kind            = "StorageV2"
        account_tier           

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

Thanks @cschleiden for making the change in your other extension. I think we should do the same thing on this one. While there is definite uses for action-provider I think the default and more common experience should be action. This will be better performing and a better default.

Before opening an issue please read this.

Are you reporting a bug or a feature request ?

• Bug
• Feature request

Description

%LOCALAPPDATA%\Yarn\bin should be prependend to path in order to enable yarn global add to work properly

System information

VSTS or TFS:

• VSTS
• [X