Matt Mitchell
Matt Mitchell
Should be able to query on branch (github or azdo). Without this build lookup in Darc is hard.
Add an API which allows for a default channel to be updated, rather than having to delete and recreate the default channel. The basic rule is that a channel may...
@dougbu commented on [Wed Jul 03 2019](https://github.com/dotnet/core-eng/issues/6876) `darc get-repository-policies` lacks options that could / should be copied over from `darc get-subscriptions`. The one I miss the most is `--regex`. `--exact`...
@dougbu commented on [Wed Jul 03 2019](https://github.com/dotnet/core-eng/issues/6878) Currently the only `darc` commands related to repository policies are `get-repository-policies` and `set-repository-policies`. While that covers CRU because `set-repository-policies` both creates and updates...
Enable an audit trail of changes made to various tables in the DB. Track: - Action (e.g. enabled, disabled, deleted, added, etc.) - What (default channel, build channel, etc.) -...
@dougbu commented on [Wed Jul 03 2019](https://github.com/dotnet/core-eng/issues/6873) `darc get-subscriptions` confusingly shows non-empty policies for batchable subscriptions. If this command is going to display repository policies, it should be clear the...
- [ ] This issue is blocking - [ ] This issue is causing unreasonable pain delete-subscriptions and a few other commands have 'mass' modes, where they match inputs on...
We should gather publishing metrics for each publish, so that we can track some key items which may affect performance: - Number of files - How big is the input...
@dougbu commented on [Wed Jul 03 2019](https://github.com/dotnet/core-eng/issues/6879) Today, "repository merge policies" are actually branch-specific. At least for ASP.NET Core, we have no reason to vary the policies per-branch. Suggest making...
Subscriptions today are all or nothing. When a build comes in, all assets that apply the target repo/branch will be applied. This is fine most of the time, but we...