nixpkgs/.github/workflows/no-channel.yml

name: "No channel PR"

on:
  pull_request:
    branches:
      - 'nixos-**'
      - 'nixpkgs-**'

permissions:
  contents: read

jobs:
  fail:
    permissions:
      contents: none
    name: "This PR is is targeting a channel branch"
    runs-on: ubuntu-latest
    steps:
    - run: |
        cat <<EOF
        The nixos-* and nixpkgs-* branches are pushed to by the channel
        release script and should not be merged into directly.

        Please target the equivalent release-* branch or master instead.
        EOF
        exit 1
ci: add no-channel check (#109543) * ci: add no-channel check * Update .github/workflows/no-channel.yml Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com> Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com> 2021-07-21 09:22:37 +03:00			`name: "No channel PR"`

			`on:`
			`pull_request:`
			`branches:`
			`- 'nixos-**'`
			`- 'nixpkgs-**'`

chore: Set permissions for GitHub actions Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: nathannaveen <42319948+nathannaveen@users.noreply.github.com> 2022-07-04 04:09:50 +03:00			`permissions:`
			`contents: read`

ci: add no-channel check (#109543) * ci: add no-channel check * Update .github/workflows/no-channel.yml Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com> Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com> 2021-07-21 09:22:37 +03:00			`jobs:`
			`fail:`
chore: Set permissions for GitHub actions Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: nathannaveen <42319948+nathannaveen@users.noreply.github.com> 2022-07-04 04:09:50 +03:00			`permissions:`
			`contents: none`
ci: add no-channel check (#109543) * ci: add no-channel check * Update .github/workflows/no-channel.yml Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com> Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com> 2021-07-21 09:22:37 +03:00			`name: "This PR is is targeting a channel branch"`
			`runs-on: ubuntu-latest`
			`steps:`
			`- run: \|`
			`cat <<EOF`
			`The nixos-* and nixpkgs-* branches are pushed to by the channel`
			`release script and should not be merged into directly.`

			`Please target the equivalent release-* branch or master instead.`
			`EOF`
			`exit 1`