Per the tox documentation is mentions that the parallel_show_output setting is a global [tox] setting however this doesn't seem to be the case, i.e., if one's tox.ini file is of the form:

[tox]
parallel_show_output = true

then running tox --parallel auto does not show any output.

According to t

According to GitHub's docs on CODEOWNERS, a code owner can be either a team name or a username. Bors doesn't support the latter.

Adding documentation example of a working CI build using cirrus-ci.org (.cirrus.yml)

Another use case to document; changing the client's class, and how to autowire that to another own service definition.

Possible content

The bundle can get used as "a factory" to create an autowireable class. That way the bundle puts the middleware (like logging / error reporting / timing) in place.

<?php

namespace Acme\Infra\Shopping;

class Client extends \GuzzleHttp\Clie

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

Since us Azure Pipelines people keep introducing changes that break Pipelines for other people, I think it would be useful if there were build checks that ran in Azure Pipelines for the 3 conditions, YAML, Classic Build, and Classic Release. It could be as simple as just running Set-BuildEnvironment because the bugs we're fixing are the result of that breaking, but it would probably make sense

Allow editing of story point for a story in JIRA, currently it's display only

Build started
2$ErrorActionPreference = "Stop"
3Invoke-WebRequest http://raw.github.com/krlmlr/r-appveyor/master/scripts/appveyor-tool.ps1 -OutFile "..\appveyor-tool.ps1"
4Import-Module '..\appveyor-tool.ps1'
5
6git clone -q --branch=master https://github.com/Mathelab/IntLIM.git C:\projects\intlim
7git checkout -qf b4e649d20e296fa7d0b5bfdf07bcc6973d2815a9
8Running Install scripts
9Bootstra

I'm not sure if I've stumbled into a real issue, or just fallen into a documentation hole.

I had a bear of a time getting travis-ci set up this time. When I use run_tests --coverage, I get a timeout waiting for ST3 to respond. When I use run_tests without coverage, they run fine. The raw logs for both runs show the bootstrap installing sublime-coverage:

...
Running command: bootstrap 

This related to hpi-swa/smalltalkCI#218 , the problem why my tests weren't executed is that I stated DynaCASE-Demo.* in the packages list, but the actual name was DynaCASE-DEMO.*.

Preferably it should be case-insensitive (it is not normal to distinguish package names just by capitalization), but in either case there should be a warning, because I can make a typo or s