-
-
Notifications
You must be signed in to change notification settings - Fork 514
feat: Add new workflow to update the maintainers servers list #3010
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 2 commits
9c13fe4
4e6bc7c
5398b44
232728c
6f3fbdd
9971b2a
80616b0
afc2d3d
b72a1f8
fbd3a02
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
| @@ -0,0 +1,50 @@ | ||||
| name: Update servers list | ||||
| on: | ||||
| workflow_dispatch: | ||||
| schedule: | ||||
| - cron: "11 3 1 */2 *" # Run at 03:11 on the 1st of every 2nd month | ||||
| jobs: | ||||
| update-servers-list: | ||||
| if: github.repository == 'qdm12/gluetun' | ||||
| runs-on: ubuntu-latest | ||||
| permissions: | ||||
| actions: read | ||||
| contents: write | ||||
| pull-requests: write | ||||
| steps: | ||||
| - uses: actions/checkout@v6 | ||||
|
|
||||
| - name: Setup Go | ||||
| uses: actions/setup-go@v6 | ||||
shwoop marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||
| with: | ||||
| go-version-file: go.mod | ||||
|
|
||||
| - name: Update servers list | ||||
| run: | | ||||
| go run ./cmd/gluetun/main.go update -all -maintainer -minratio 0.2 | ||||
shwoop marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||
| verify-private: |
secrets, I'll set secrets.PROTON_EMAIL and secrets.PROTON_PASSWORD for it.
shwoop marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we name that branch with the current date YYYY-MM-DD so it doesn't conflict if one doesn't get merged or isn't deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that would be overkill if it runs every two months but then I added functionality to allow manually triggering the workflow so it makes a lot of sense now.
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's keep this commented for now? So we can merge manually a few times, then fully automate
Uh oh!
There was an error while loading. Please reload this page.