Open a-a-ron opened 2 years ago
@a-a-ron I added some comments below and a question on previously added content for you.
I went through each of the modules in the summaries and content units. The most mentions of GitHub-hosted runners is in Manage GitHub Actions in the enterprise. Virtual and Images did not pop up using Find. I suggest leaving this change out, as the location may change again, since the last location is not in the information. Actions users can find that information in the blog or docs.
The manage runners unit is where I think this would fit in best. As above, the number of days is not listed, and given that the days has changed once, I think this is best suited in the blogs and docs.
@a-a-ron thoughts? Reviewing these blogs has me thinking about the section under, The table below compares GitHub-hosted runners versus self-hosted runners. Use it to choose the appropriate runner for your workload. I am rethinking this content as best suited in the blogs and docs, due to the possibility of changing and those two areas are probably updated more frequently.
@rmallorybpc sounds good. Let's leave out the mention of the changing timeline and let the docs detail that. The main thing I wanted to check is to see if we need to change anything we have to reflect the renamed from actions/virtual-environments to actions/runner-images.
Reviewing these blogs has me thinking about the section under, The table below compares GitHub-hosted runners versus self-hosted runners. Use it to choose the appropriate runner for your workload. I am rethinking this content as best suited in the blogs and docs, due to the possibility of changing and those two areas are probably updated more frequently.
I agree with changing details but I think this section is good to leave in. It's generics to picking the right type of runner. Small details may change but the recommendation between self-hosted and hosted runners is good. Let's keep it.
@rmallorybpc sounds good. Let's leave out the mention of the changing timeline and let the docs detail that. The main thing I wanted to check is to see if we need to change anything we have to reflect the renamed from actions/virtual-environments to actions/runner-images.
Reviewing these blogs has me thinking about the section under, The table below compares GitHub-hosted runners versus self-hosted runners. Use it to choose the appropriate runner for your workload. I am rethinking this content as best suited in the blogs and docs, due to the possibility of changing and those two areas are probably updated more frequently.
I agree with changing details but I think this section is good to leave in. It's generics to picking the right type of runner. Small details may change but the recommendation between self-hosted and hosted runners is good. Let's keep it.
@a-a-ron sounds good on keeping in what's in now.
I did not find any mentions of the name change that needed to be updated.
The repository that houses the images installed on GitHub-hosted runners has been renamed from actions/virtual-environments to actions/runner-images. These images are maintained by GitHub and used by GitHub Actions.
We need to scan our content to see if we have outdated references.
Source: https://github.blog/changelog/2022-08-08-github-actions-runner-images-repository-refresh/
Previously we retained self-hosted GitHub Action runners in the GitHub Actions UI for 30 days after they were last seen to connect. With the growth in the use of ephemeral runners and the scale of use of self-hosted, this is becoming hard for users to manage. As a result, we are making the following changes to the time we retain offline runners for.
A non-ephemeral self-hosted Actions runner is automatically removed from GitHub if we have not seen it connect to GitHub for more than 14 days.
An ephemeral self-hosted Actions runner is automatically removed from GitHub if we have not seen it connect to GitHub for more than one day.
Source: https://github.blog/changelog/2022-08-03-github-actions-remove-offline-self-hosted-runners/