starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[PR #5256] [MERGED] Split rolling and PR builds. Drop ARM64, X86 from PR. #26205

New Issue
Open
opened 2026-01-31 09:14:37 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:14:37 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/5256
Author: @miniksa
Created: 4/6/2020
Status: ✅ Merged
Merged: 4/6/2020
Merged by: @undefined

Base: master ← Head: dev/miniksa/builds

📝 Commits (4)

  • c647747 Separate rolling build and PR builds into their own defs. Drop ARM64 from PR as it has never found anything.
  • 6ea61ab collapse back into one def, add conditions.
  • c847249 Try with conditional stages.
  • e5e6677 Fix stage names, add display names.

📊 Changes

1 file changed (+39 additions, -17 deletions)

View changed files

📝 build/pipelines/ci.yml (+39 -17)

📄 Description

Summary of the Pull Request

Edits the definition file to distinguish further between the rolling build (the one that happens in master as it's updated) and the PR builds (that happen on every push to a pull request to master.) We will build less in PR since it rolls so often by removing the lines that reveal very few to no bugs at PR time. We'll leave them on in rolling so stuff can still be caught.

PR Checklist

  • Closes a desire to not waste builds.
  • I work here.
  • We'll see if the build still works.
  • No specific docs.
  • I talked about this with @DHowett-MSFT already.

Validation Steps Performed

  • This PR itself should validate that the definition still works in PRs. I think we have to wait for it to go to master to see if the trigger still works there.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/5256 **Author:** [@miniksa](https://github.com/miniksa) **Created:** 4/6/2020 **Status:** ✅ Merged **Merged:** 4/6/2020 **Merged by:** [@undefined](undefined) **Base:** `master` ← **Head:** `dev/miniksa/builds` --- ### 📝 Commits (4) - [`c647747`](https://github.com/microsoft/terminal/commit/c647747241961e52acc5b5fcf63879f8f2ce0372) Separate rolling build and PR builds into their own defs. Drop ARM64 from PR as it has never found anything. - [`6ea61ab`](https://github.com/microsoft/terminal/commit/6ea61abd94610b531d7163146f9b5de72fcb36bf) collapse back into one def, add conditions. - [`c847249`](https://github.com/microsoft/terminal/commit/c847249cf878fd719e6529341c8aa7f92d975427) Try with conditional stages. - [`e5e6677`](https://github.com/microsoft/terminal/commit/e5e6677c4a9e52e00876fcb780d3ccdcac30e755) Fix stage names, add display names. ### 📊 Changes **1 file changed** (+39 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `build/pipelines/ci.yml` (+39 -17) </details> ### 📄 Description ## Summary of the Pull Request Edits the definition file to distinguish further between the rolling build (the one that happens in master as it's updated) and the PR builds (that happen on every push to a pull request to master.) We will build less in PR since it rolls so often by removing the lines that reveal very few to no bugs at PR time. We'll leave them on in rolling so stuff can still be caught. ## PR Checklist * [x] Closes a desire to not waste builds. * [x] I work here. * [ ] We'll see if the build still works. * [x] No specific docs. * [x] I talked about this with @DHowett-MSFT already. ## Validation Steps Performed * [x] This PR itself should validate that the definition still works in PRs. I think we have to wait for it to go to master to see if the trigger still works there. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:14:37 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#26205
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?