[PR #374] [MERGED] Reference Only Microsoft Azue Pipelines In Readme.md #1614

New issue

Closed

opened 2026-05-05 07:57:46 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:57:46 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/debauchee/barrier/pull/374
Author: @TafThorne
Created: 7/26/2019
Status: ✅ Merged
Merged: 8/5/2019
Merged by: @AdrianKoshka

Base: master ← Head: patch-1

📝 Commits (1)

6dc59d1 Reference Only Microsoft Azue Pipelines In Readme.md

📊 Changes

1 file changed (+8 additions, -2 deletions)

View changed files

📝 README.md (+8 -2)

📄 Description

We plan to remove all the CI pipeline apart from Microsoft Azue Pipelines. This was documented under #308 after the Azure Pipeline system was successfully integrated under #303 and shown to provide all the build targetes we needed.

As there are presently have 4 seperate main build targes. As well as giving the overall master branch status in the Readme (which forms part of the main page on github.com) also show the seperate build status. This makes it clear if a single part fails and gives an obvious indicator that this project works for Linux, Mac and Windows.

_{🔄 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/debauchee/barrier/pull/374 **Author:** [@TafThorne](https://github.com/TafThorne) **Created:** 7/26/2019 **Status:** ✅ Merged **Merged:** 8/5/2019 **Merged by:** [@AdrianKoshka](https://github.com/AdrianKoshka) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`6dc59d1`](https://github.com/debauchee/barrier/commit/6dc59d14a33a2564520bd8f95f742a934728a414) Reference Only Microsoft Azue Pipelines In Readme.md ### 📊 Changes **1 file changed** (+8 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+8 -2) </details> ### 📄 Description We plan to remove all the CI pipeline apart from Microsoft Azue Pipelines. This was documented under #308 after the Azure Pipeline system was successfully integrated under #303 and shown to provide all the build targetes we needed. As there are presently have 4 seperate main build targes. As well as giving the overall master branch status in the Readme (which forms part of the main page on github.com) also show the seperate build status. This makes it clear if a single part fails and gives an obvious indicator that this project works for Linux, Mac and Windows. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>