[PR #455] [MERGED] Create ci.yaml #1095

Closed
opened 2026-05-05 07:04:32 -06:00 by gitea-mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/MonitorControl/MonitorControl/pull/455
Author: @stephengroat
Created: 6/17/2021
Status: Merged
Merged: 8/4/2021
Merged by: @JoniVR

Base: masterHead: patch-1


📝 Commits (1)

📊 Changes

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

View changed files

.github/workflows/ci.yaml (+7 -0)

📄 Description

@JoniVR

got a message from Github, need to enable a workflow to enable the macos-11 stuff

Hi!

 

Contacting you as you have submitted the form to join macOS 11 pool on GitHub Actions.

We are enabling pool by the unique key that is autogenerated upon the first Actions usage. We were unable to identify such keys for your organization\account, because likely you have never used Actions. Please, run at least one workflow with Actions to trigger key generation. The exact image doesn’t matter, you can use any OS.

 

Sorry for inconveniences. Please, let me know if you have any questions.

 

Thanks,

Alyona.

🔄 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/MonitorControl/MonitorControl/pull/455 **Author:** [@stephengroat](https://github.com/stephengroat) **Created:** 6/17/2021 **Status:** ✅ Merged **Merged:** 8/4/2021 **Merged by:** [@JoniVR](https://github.com/JoniVR) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`8ba3500`](https://github.com/MonitorControl/MonitorControl/commit/8ba350090d52250e8f7cc4d3c564f8b9abba9aa6) Create ci.yaml ### 📊 Changes **1 file changed** (+7 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/ci.yaml` (+7 -0) </details> ### 📄 Description @JoniVR got a message from `Github`, need to enable a workflow to enable the `macos-11` stuff ``` Hi! Contacting you as you have submitted the form to join macOS 11 pool on GitHub Actions. We are enabling pool by the unique key that is autogenerated upon the first Actions usage. We were unable to identify such keys for your organization\account, because likely you have never used Actions. Please, run at least one workflow with Actions to trigger key generation. The exact image doesn’t matter, you can use any OS. Sorry for inconveniences. Please, let me know if you have any questions. Thanks, Alyona. ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
gitea-mirror 2026-05-05 07:04:32 -06:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#1095
No description provided.