scoopinstaller / buckettemplate

Template Bucket for Scoop Installer

Scoop Bucket Template

Template bucket for Scoop, the Windows command-line installer.

How do I use this template?

1. Generate your own copy of this repository with the "Use this template" button.
2. Allow all GitHub Actions:
   • Navigate to Settings - Actions - General - Actions permissions.
   • Select Allow all actions and reusable workflows.
   • Then Save.
3. Allow writing to the repository from within GitHub Actions:
   • Navigate to Settings - Actions - General - Workflow permissions.
   • Select Read and write permissions.
   • Then Save.
4. Document the bucket in README.md.
5. Replace the placeholder repository string in bin/auto-pr.ps1.
6. Create new manifests by copying bucket/app-name.json.template to bucket/<app-name>.json.
7. Commit and push changes.
8. If you'd like your bucket to be indexed on https://scoop.sh, add the topic scoop-bucket to your repository.

How do I install these manifests?

After manifests have been committed and pushed, run the following:

scoop bucket add <bucketname> https://github.com/<username>/<bucketname>
scoop install <bucketname>/<manifestname>

How do I contribute new manifests?

To make a new manifest contribution, please read the Contributing Guide and App Manifests wiki page.

buckettemplate's Issues

[Bug]: Excavator action fails due to permisisons

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues/PRs to ensure it has not already been reported or fixed.
• I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

N/A

Expected/Current Behaviour

The Excavator job should complete without failure.

Steps to Reproduce

I create a new bucket repository from this template. The Excavator job has always failed with this message:

$ git push origin master
remote: Permission to my/bucket.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/my/bucket.git/': The requested URL returned error: 403

Possible Solution

Excavator workflow should state needed permissions

on:
  workflow_dispatch:
  schedule:
    # run every 4 hours
    - cron: '20 */4 * * *'
permissions:
  contents: write
name: Excavator
jobs:
  excavate:
    name: Excavate
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@main
      - name: Excavate
        uses: ScoopInstaller/GithubActions@main
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          SKIP_UPDATED: 1

Scoop and Buckets Version

N/A - GitHub Actions issue

Scoop Config

N/A - GitHub Actions issue

PowerShell Version

N/A - GitHub Actions issue

Additional Softwares

No response

[Feature] Update CI/GitHub Action in GenericBucket

Feature Request

Sorry if this is not the right place to ask, I can't open issue in GenericBucket.

Is your feature request related to a problem? Please describe.

GenericBucket doesn't have the same feature as known bucket because it's using old yml file and old repo for GitHub Action, is this intentional or you guys forgot to update it?

Describe the solution you'd like

Use .github folder from known bucket for GenericBucket and also add appveyor.yml(?)

I also have some question:

• Does the autoupdate thingy comitted by github-action bot is what you guys called Excavator?
• Does it run purely on github action (dont need to set up anything outside github)?

How to make my bucket not indexed by scoop search engine?

Hi, I want to make a testing bucket, how do I make them not detected by scoop search engine like ScoopSearch and scoop-directory ?

[Bug]: GH action Excavator gives no feedback for 404 errors in autoupdates

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues/PRs to ensure it has not already been reported or fixed.
• I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

N/A

Expected/Current Behaviour

I'm hoping that a change to the Excavator GitHub action can provide direct feedback when an autoupdate action fails. Currently, if such an error occurs, the Excavator just seems to have succeeded without any errors. As such, problems will only be detected by manually going through the logs and it will seem like there weren't any updates for the application.

More generally, it would be desirable that any ERROR output by scoop results in a warning on the GitHub Action level.

In the Action log:

Autoupdating betterbird-future
Downloading somethingsomething.installer.exe to compute hashes!
The remote server returned an error: (404) Not Found.
URL https://something.something/somethingsomething.installer.exe#/dl.7z is not valid
ERROR Could not update something, hash for somethingsomething.installer.exe failed!

Steps to Reproduce

1. Have a bucket that uses Excavator
2. Change in some manifest the `autoupdate`->`architecture`->`*`->`url` to something that results in a 404 error
3. Have an update ready for the corresponding application or change to a previous version in the manifest
4. Let Excavator run and seemingly complete successfully

Possible Solution

Probably something to react to errorlevels or an error/failed env. variable?

Scoop and Buckets Version

N/A

Scoop Config

N/A

PowerShell Version

N/A

Additional Softwares

No response

[Bug]: Test workflow Could not find a project

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues/PRs to ensure it has not already been reported or fixed.
• I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

N/A

Expected/Current Behaviour

This template actions

Steps to Reproduce

https://github.com/Jvcon/werkzeuge/actions/runs/5816070288

Possible Solution

N/A

Scoop and Buckets Version

N/A

Scoop Config

N/A

PowerShell Version

N/A

Additional Softwares

No response