Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[Rollout] Production rollout 2026-06-16 - #6405

#6405
Merged
premun merged 17 commits into
dotnet:productiondotnet/arcade-services:productionfrom
dkurepa:rollout/2026-06-16dkurepa/arcade-services:rollout/2026-06-16Copy head branch name to clipboard
Jun 16, 2026
Merged

[Rollout] Production rollout 2026-06-16#6405
premun merged 17 commits into
dotnet:productiondotnet/arcade-services:productionfrom
dkurepa:rollout/2026-06-16dkurepa/arcade-services:rollout/2026-06-16Copy head branch name to clipboard

Conversation

@dkurepa

@dkurepa dkurepa commented Jun 16, 2026

Copy link
Copy Markdown
Member

#6404

Checklist

  • Verify this PR contains the expected changes
  • Follow the rollout process in issue Rollout 2026-06-16 #6404
  • ⚠️ DO NOT SQUASH when merging - use merge commit

dkurepa and others added 17 commits June 9, 2026 16:23
I detected changes in the production branch which have not been merged
yet to main. I'm a robot and am configured to help you automatically
keep main up to date, so I've opened this PR.

This PR merges commits made on production by the following committers:

* @dkurepa

## Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete
this PR by creating a merge commit, *not* a squash or rebase commit.

<img alt="merge button instructions"
src="https://i.imgur.com/GepcNJV.png" width="300" />

If this repo does not allow creating merge commits from the GitHub UI,
use command line instructions.

## Instructions for merging via command line

Run these commands to merge this pull request from the command line.

``` sh
git fetch
git checkout production
git pull --ff-only
git checkout main
git pull --ff-only
git merge --no-ff production

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet/arcade-services HEAD:merge/production-to-main
```

<details>
<summary>or if you are using SSH</summary>

```
git push git@github.com:dotnet/arcade-services HEAD:merge/production-to-main
```

</details>


After PR checks are complete push the branch
```
git push
```

## Instructions for resolving conflicts

:warning: If there are merge conflicts, you will need to resolve them
manually before merging. You can do this [using GitHub][resolve-github]
or using the [command line][resolve-cli].

[resolve-github]:
https://help.github.com/articles/resolving-a-merge-conflict-on-github/
[resolve-cli]:
https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

## Instructions for updating this pull request

Contributors to this repo have permission update this pull request by
pushing to the branch 'merge/production-to-main'. This can be done to
resolve conflicts or make other changes to this pull request before it
is merged.
The provided examples assume that the remote is named 'origin'. If you
have a different remote name, please replace 'origin' with the name of
your remote.

```
git fetch
git checkout -b merge/production-to-main origin/main
git pull https://github.com/dotnet/arcade-services merge/production-to-main
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/arcade-services HEAD:merge/production-to-main
```

<details>
    <summary>or if you are using SSH</summary>

```
git fetch
git checkout -b merge/production-to-main origin/main
git pull git@github.com:dotnet/arcade-services merge/production-to-main
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/arcade-services HEAD:merge/production-to-main
```

</details>

Contact .NET Core Engineering (dotnet/dnceng) if you have questions or
issues.
Also, if this PR was generated incorrectly, help us fix it. See
https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

---------

Co-authored-by: Djuradj Kurepa <91743470+dkurepa@users.noreply.github.com>
Currently if the message is too long, we don't see it fully
<img width="1950" height="112" alt="image"
src="https://github.com/user-attachments/assets/1240b9f0-e84a-4894-9638-12259e01585e"
/>

This PR adds a slider so the error can be fully read
<img width="1999" height="96" alt="image"
src="https://github.com/user-attachments/assets/fab4dfbb-4398-4714-a22b-7f97a3b8e83b"
/>

dotnet#6334
`darc vmr` commands (e.g. `resolve-conflict`) make temporary local
commits during codeflow. Users with GPG signing enabled globally get
interrupted by signing-password prompts mid-operation.

All codeflow commits route through a small set of central git commit
invocations, each now passes `--no-gpg-sign`:

- **`LocalGitClient.CommitAsync`** — primary commit path used by all Vmr
flowers and conflict resolvers (`VmrManagerBase`, `WorkBranch`,
`VmrBackFlower`, `CodeFlowConflictResolver`, `VmrCodeflower`).
- **`LocalGitClient.CommitAmendAsync`** — amend commits.
- **`RemoteRepoBase`** — the remaining direct `git commit` in the
PR-creation path.

```csharp
IEnumerable<string> args = new[] { "commit", "--no-gpg-sign", "-m", message };
```

Merge/rebase steps in `WorkBranch` use `--no-commit`/`--squash` and
finalize via `CommitAsync`, so they're covered by the central change.
dotnet#6334
Previously we were dedicating 40% of the screen to the sub name, which
looked bad on both big and small screens. This makes it a fixed width
<img width="2420" height="190" alt="image"
src="https://github.com/user-attachments/assets/38c2ff39-7450-41c4-91be-44c3ffee4882"
/>
dotnet#6190

Features:
- Displays 100 latest outcomes based on filters
- Paging is implemented based on date. There is a "Load more" button
that loads the next 100 results using the last result's date as the new
date limit.
- Filters can be applied via URLs, allowing us to link to a specific
subscription's outcomes on other BarViz pages
- Clicking a subscription id leads to the subscriptions page (I will
change this so that it opens the small subscription popup instead)
- Each status has a color assigned
Signed-off-by: dependabot[bot] <support@github.com>
…8 to 10.0.9 (dotnet#6401)

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: dependabot[bot] <support@github.com>
@premun
premun enabled auto-merge June 16, 2026 11:02
@premun
premun disabled auto-merge June 16, 2026 11:06
@premun
premun merged commit 4dd67f5 into dotnet:production Jun 16, 2026
8 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.