github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-16 08:33:59 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[PR #2040] [MERGED] Add workaround for broken windows 2022 runner #3313

New Issue
Closed
opened 2025-11-26 23:31:06 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-26 23:31:06 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/2040
Author: @joseph-flinn
Created: 8/16/2022
Status: ✅ Merged
Merged: 8/16/2022
Merged by: @joseph-flinn

Base: master ← Head: patch/workaround-for-broken-windows-2022-runner

📝 Commits (2)

  • 6ddf05a Add workaround for broken windows 2022 runner
  • 6451a63 Adding workaround to F-Droid job

📊 Changes

1 file changed (+40 additions, -0 deletions)

View changed files

📝 .github/workflows/build.yml (+40 -0)

📄 Description

Type of change

  • Bug fix
  • New feature development
  • Tech debt (refactoring, code cleanup, dependency upgrades, etc)
  • Build/deploy pipeline (DevOps)
  • Other

Objective

Add workaround for broken windows 2022 runner.

Before you submit

  • I have checked for formatting errors (dotnet tool run dotnet-format --check) (required)
  • I have added unit tests where it makes sense to do so (encouraged but not required)
  • This change requires a documentation update (notify the documentation team)
  • This change has particular deployment requirements (notify the DevOps team)

🔄 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/bitwarden/android/pull/2040 **Author:** [@joseph-flinn](https://github.com/joseph-flinn) **Created:** 8/16/2022 **Status:** ✅ Merged **Merged:** 8/16/2022 **Merged by:** [@joseph-flinn](https://github.com/joseph-flinn) **Base:** `master` ← **Head:** `patch/workaround-for-broken-windows-2022-runner` --- ### 📝 Commits (2) - [`6ddf05a`](https://github.com/bitwarden/android/commit/6ddf05a1fa6e487716064a326993c447eeeeba3b) Add workaround for broken windows 2022 runner - [`6451a63`](https://github.com/bitwarden/android/commit/6451a6373ed0bb68da2ff27638672a93cbc9ea9a) Adding workaround to F-Droid job ### 📊 Changes **1 file changed** (+40 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/build.yml` (+40 -0) </details> ### 📄 Description ## Type of change - [ ] Bug fix - [ ] New feature development - [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc) - [X] Build/deploy pipeline (DevOps) - [ ] Other ## Objective <!--Describe what the purpose of this PR is. For example: what bug you're fixing or what new feature you're adding--> Add workaround for broken windows 2022 runner. ## Before you submit - [ ] I have checked for formatting errors (`dotnet tool run dotnet-format --check`) (required) - [ ] I have added **unit tests** where it makes sense to do so (encouraged but not required) - [ ] This change requires a **documentation update** (notify the documentation team) - [ ] This change has particular **deployment requirements** (notify the DevOps team) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-26 23:31:06 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#3313
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?