shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-25 10:04:04 +03:00
Code
systemd/.github/workflows/development_freeze.yml

44 lines
1.2 KiB
YAML
Raw Normal View History

ci(dev-freeze): Use GitHub Action for PR comments GitHub Action `devel-freezer` helps with development freeze notifications during the RC phase. It will create comments using predefined messages on newly created and updated PRs when the RC tag has been released. Also, it will update comments once a new major version has been released. Documentation available at: https://github.com/redhat-plumbers-in-action/devel-freezer
2022-10-12 15:37:00 +02:00
# doc: https://github.com/redhat-plumbers-in-action/devel-freezer#readme
---
name: Development Freeze
on:
ci: Fix Development Freeze Automation Due to the limitation of `GITHUB_TOKEN` when running workflows from forks, it's required to split the `development_freeze` workflow in two. * First workflow will run on the `pull_request` trigger and save the PR number in the artifact. This workflow is running with read-only permissions on `GITHUB_TOKEN`. * Second workflow will get triggered on `workflow_run`. It will be run directly in the `systemd/systemd` context and can get permission to be able to create comments on PR. GITHUB_TOKEN limitations: * https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token GitHub Security Labs Article - How to correctly and safely overcome GITHUB_TOKEN limitations: * https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
2023-02-03 10:25:51 +01:00
workflow_run:
workflows: [ Gather Pull Request Metadata ]
types:
- completed
ci(dev-freeze): Use GitHub Action for PR comments GitHub Action `devel-freezer` helps with development freeze notifications during the RC phase. It will create comments using predefined messages on newly created and updated PRs when the RC tag has been released. Also, it will update comments once a new major version has been released. Documentation available at: https://github.com/redhat-plumbers-in-action/devel-freezer
2022-10-12 15:37:00 +02:00
permissions:
contents: read
jobs:
freezer:
ci: Fix Development Freeze Automation Due to the limitation of `GITHUB_TOKEN` when running workflows from forks, it's required to split the `development_freeze` workflow in two. * First workflow will run on the `pull_request` trigger and save the PR number in the artifact. This workflow is running with read-only permissions on `GITHUB_TOKEN`. * Second workflow will get triggered on `workflow_run`. It will be run directly in the `systemd/systemd` context and can get permission to be able to create comments on PR. GITHUB_TOKEN limitations: * https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token GitHub Security Labs Article - How to correctly and safely overcome GITHUB_TOKEN limitations: * https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
2023-02-03 10:25:51 +01:00
if: >
github.event.workflow_run.event == 'pull_request' &&
github.event.workflow_run.conclusion == 'success' &&
github.repository == 'systemd/systemd'
ci(dev-freeze): Use GitHub Action for PR comments GitHub Action `devel-freezer` helps with development freeze notifications during the RC phase. It will create comments using predefined messages on newly created and updated PRs when the RC tag has been released. Also, it will update comments once a new major version has been released. Documentation available at: https://github.com/redhat-plumbers-in-action/devel-freezer
2022-10-12 15:37:00 +02:00
runs-on: ubuntu-22.04
permissions:
pull-requests: write
steps:
ci(freezer): update metadata and development_freeze workflow use custom action to gather PR metadata and download artifact rather then inline script
2024-03-20 10:32:07 +01:00
- id: artifact
name: Download Pull Request Metadata artifact
uses: redhat-plumbers-in-action/download-artifact@463ae626ac2dd333491c7beccaa24c12c5c259b8
ci: Fix Development Freeze Automation Due to the limitation of `GITHUB_TOKEN` when running workflows from forks, it's required to split the `development_freeze` workflow in two. * First workflow will run on the `pull_request` trigger and save the PR number in the artifact. This workflow is running with read-only permissions on `GITHUB_TOKEN`. * Second workflow will get triggered on `workflow_run`. It will be run directly in the `systemd/systemd` context and can get permission to be able to create comments on PR. GITHUB_TOKEN limitations: * https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token GitHub Security Labs Article - How to correctly and safely overcome GITHUB_TOKEN limitations: * https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
2023-02-03 10:25:51 +01:00
with:
ci(freezer): update metadata and development_freeze workflow use custom action to gather PR metadata and download artifact rather then inline script
2024-03-20 10:32:07 +01:00
name: Pull Request Metadata
ci: Fix Development Freeze Automation Due to the limitation of `GITHUB_TOKEN` when running workflows from forks, it's required to split the `development_freeze` workflow in two. * First workflow will run on the `pull_request` trigger and save the PR number in the artifact. This workflow is running with read-only permissions on `GITHUB_TOKEN`. * Second workflow will get triggered on `workflow_run`. It will be run directly in the `systemd/systemd` context and can get permission to be able to create comments on PR. GITHUB_TOKEN limitations: * https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token GitHub Security Labs Article - How to correctly and safely overcome GITHUB_TOKEN limitations: * https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
2023-02-03 10:25:51 +01:00
- name: Repository checkout
build(deps): bump actions/checkout from 4.1.1 to 4.1.2 Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.1 to 4.1.2. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/b4ffde65f46336ab88eb53be808477a3936bae11...9bb56186c3b09b4f86b1c65136769dd318469633) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-13 16:48:43 +00:00
uses: actions/checkout@9bb56186c3b09b4f86b1c65136769dd318469633
ci(dev-freeze): Use GitHub Action for PR comments GitHub Action `devel-freezer` helps with development freeze notifications during the RC phase. It will create comments using predefined messages on newly created and updated PRs when the RC tag has been released. Also, it will update comments once a new major version has been released. Documentation available at: https://github.com/redhat-plumbers-in-action/devel-freezer
2022-10-12 15:37:00 +02:00
with:
fetch-depth: 0
- name: Development Freezer
ci(freezer): update `devel-freezer` GHA to `v1.1.0` The new version of `devel-freezer` GitHub Action adds support for milestones, labels, and more. Now, when the `rc` tag is published, it won't post a development freeze comment on PRs included in the next milestone. This commit also sets a delay of the 20s for PR validation to give some time for updating labels and milestones on submitted PRs.
2024-03-20 12:37:18 +01:00
uses: redhat-plumbers-in-action/devel-freezer@396c94ba8cb417474e6626c83a42addea210a403
ci(dev-freeze): Use GitHub Action for PR comments GitHub Action `devel-freezer` helps with development freeze notifications during the RC phase. It will create comments using predefined messages on newly created and updated PRs when the RC tag has been released. Also, it will update comments once a new major version has been released. Documentation available at: https://github.com/redhat-plumbers-in-action/devel-freezer
2022-10-12 15:37:00 +02:00
with:
ci(freezer): update metadata and development_freeze workflow use custom action to gather PR metadata and download artifact rather then inline script
2024-03-20 10:32:07 +01:00
pr-number: ${{ fromJSON(steps.artifact.outputs.pr-metadata-json).number }}
ci(freezer): update `devel-freezer` GHA to `v1.1.0` The new version of `devel-freezer` GitHub Action adds support for milestones, labels, and more. Now, when the `rc` tag is published, it won't post a development freeze comment on PRs included in the next milestone. This commit also sets a delay of the 20s for PR validation to give some time for updating labels and milestones on submitted PRs.
2024-03-20 12:37:18 +01:00
# delay start of validation to allow for some milestone/labels tweaking
delay: 20
ci(dev-freeze): Use GitHub Action for PR comments GitHub Action `devel-freezer` helps with development freeze notifications during the RC phase. It will create comments using predefined messages on newly created and updated PRs when the RC tag has been released. Also, it will update comments once a new major version has been released. Documentation available at: https://github.com/redhat-plumbers-in-action/devel-freezer
2022-10-12 15:37:00 +02:00
token: ${{ secrets.GITHUB_TOKEN }}
Copy Permalink