Skip to content

Adding workflow for beta packages #264

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.

Sign up for GitHub

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

Open
h7io wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Adding workflow for beta packages #264

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1839cb8
add workflow for packaging nightly builds
h7io Apr 8, 2022
af9cf77
use github-action bot's email for commits
h7io Apr 8, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions .github/workflows/update-nightly.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# adapted from https://github.com/flathub/com.github.wwmm.easyeffects/blob/master/.github/workflows/update-beta.yml
name: Check for nightly updates in beta branch
on:
schedule:
- cron: "0 5,6 * * *" # run twice very 24 hours, a scheduled workflow only runs if in the default branch.
# We need to run a second time so it can be automatically merged.
workflow_dispatch:

jobs:
flatpak-external-data-checker:
runs-on: ubuntu-latest
container:
image: ghcr.io/flathub/flatpak-external-data-checker

steps:
- uses: actions/checkout@v2
with:
ref: beta # with this workflow, f-e-d-c will specifically checkout and submit a PR against beta, not master.

- uses: docker://ghcr.io/flathub/flatpak-external-data-checker:latest
env:
GIT_AUTHOR_NAME: Flatpak External Data Checker
GIT_COMMITTER_NAME: Flatpak External Data Checker
GIT_AUTHOR_EMAIL: ${{ github.actor }}@users.noreply.github.com
GIT_COMMITTER_EMAIL: ${{ github.actor }}@users.noreply.github.com
EMAIL: ${{ github.actor }}@users.noreply.github.com

@vchernin vchernin Apr 8, 2022 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable, note you might want to change the email to something generic, otherwise the bot- created commits might be under your name.

@vchernin vchernin Apr 8, 2022

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

E.g. perhaps the GitHub actions bot email will work? https://github.community/t/github-actions-bot-email-address/17204/6

@h7io h7io Apr 8, 2022

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, thanks. I have changed the email-related environment variables. I don't know what the EMAIL one is meant for, but I changed it too.

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
args: --update --never-fork im.riot.Riot.yaml