# GithubActions

**Repository Path**: mirrors_shiena/GithubActions

## Basic Information

- **Project Name**: GithubActions
- **Description**: Github Actions for Scoop buckets
- **Primary Language**: Unknown
- **License**: MIT
- **Default Branch**: test
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2022-08-31
- **Last Updated**: 2026-04-26

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Github Actions for Scoop buckets

Set of automated actions, which bucket maintainers can use to save time managing issues / pull requests.

## Available environment variables

1. `GITHUB_TOKEN`
    - **REQUIRED**
    - Use `${{ secrets.GITHUB_TOKEN }}`
1. `USER_EMAIL`
    - String
    - Optional
1. `SCOOP_BRANCH`
    - String
    - If specified, scoop config 'SCOOP_BRANCH' will be configured and scoop updated
1. `SKIP_UPDATED`
    - String. Use `'1'` or `'0'`
    - If enabled, log of checkver utility will not print latest versions
1. `THROW_ERROR`
    - String. Use `'1'` or `'0'`
    - If enabled, error from checkver utility will be thrown as exception and cause the run to fail
1. `SPECIAL_SNOWFLAKES`
    - String
    - List of manifest names joined with `,` used as parameter for auto-pr utility.

## Available actions

### Excavator

- [Protected default branches are not supported.](https://github.community/t5/GitHub-Actions/How-to-push-to-protected-branches-in-a-GitHub-Action/m-p/30710/highlight/true#M526)
- Periodically execute automatic updates for all manifests
- Refer to [workflow triggers](https://help.github.com/en/articles/events-that-trigger-workflows#scheduled-events) for configuration formats

### Issues

As soon as a new issue **is created** or the **label `verify` is added** to an issue, the action is executed.
Based on the issue title, a specific sub-action is executed.
It could be one of these:

- **Hash check fails**
    1. Checkhashes binary is executed for manifest in title
    1. Result is parsed
        1. Hash mismatch
            1. Pull requests with name `<manifest>@<version>: Fix hash` are listed
                1. There is PR already
                    1. The newest one is selected
                    1. Description of this PR is updated with closing directive for created issue
                    1. Comment to issue is posted with reference to PR
                    1. Label `duplicate` added
                1. If none
                    1. New branch `<manifest>-hash-fix-<random>` is created
                    1. Changes are commited
                    1. New PR is created from this branch
            1. Labels `hash-fix-needed`, `verified` are added
        1. No problem
            1. Comment on issue is posted about hashes being right and possible causes
            1. Label `hash-fix-needed` is removed
            1. Issue is closed
        1. Binary error
            1. Label `manifest-fix-needed` is added
- **Download failed**
    1. All urls defined in manifest are retrieved
    1. Downloading of all urls is executed
    1. Comment to issue is posted
        1. If there is problematic URL
            1. List of these URLs is attached in comment
            1. Labels `manifest-fix-needed`, `verified`, `help wanted` are added
        1. All URLs could be downloaded without problem
            1. Possible causes are attached in comment

### Pull Requests

As soon as a PR **is created** or the **comment `/verify` is posted** to it, validation tests are executed (see [wiki](https://github.com/ScoopInstaller/GithubActions/wiki/Pull-Request-Checks)) for detailed desciption):

- ❗❗ **Pull request created from forked repository cannot be verified due to security concern from GitHub side** ❗❗
    - Manual `/verify` comment is needed

#### Overview of validatiors

1. Required properties (`License`, `Description`) are in place
1. Hashes of files are correct
1. Checkver functionality
1. Autoupdate functionality
    1. Hash extraction finished

## Example workflows for all actions

- Names could be changed as desired
- `if` statements are not required
    - There are only time savers when finding appropriate action log
    - Save GitHub resources

```yml
#.github\workflows\schedule.yml
on:
  schedule:
  - cron: '*/30 * * * *'
name: Excavator
jobs:
  excavate:
    name: Excavator
    runs-on: windows-latest
    steps:
    - uses: actions/checkout@main
    - name: Excavator
      uses: ScoopInstaller/Scoop-GithubActions@main
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        SKIP_UPDATED: '1'
        THROW_ERROR: '0'

#.github\workflows\issues.yml
on:
  issues:
    types: [ opened, labeled ]
name: Issue
jobs:
  issueHandler:
    name: Issue Handler
    runs-on: windows-latest
    steps:
    - uses: actions/checkout@main
    - name: Issue Handler
      uses: ScoopInstaller/Scoop-GithubActions@main
      if: github.event.action == 'opened' || (github.event.action == 'labeled' && contains(github.event.issue.labels.*.name, 'verify'))
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

#.github\workflows\issue_commented.yml
on:
  issue_comment:
    types: [ created ]
name: Commented Pull Request
jobs:
  pullRequestHandler:
    name: Pull Request Validator
    runs-on: windows-latest
    steps:
    - uses: actions/checkout@main
    - name: Pull Request Validator
      uses: ScoopInstaller/Scoop-GithubActions@main
      if: startsWith(github.event.comment.body, '/verify')
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

#.github\workflows\pull_request.yml
on:
  pull_request:
    types: [ opened ]
name: Pull Requests
jobs:
  pullRequestHandler:
    name: Pull Request Validator
    runs-on: windows-latest
    steps:
    - uses: actions/checkout@main
    - name: Pull Request Validator
      uses: ScoopInstaller/Scoop-GithubActions@main
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```