Files
actual/.github/workflows/fork-pr-welcome.yml
Matiss Janis Aboltins bba89d1fd8 [AI] Migrate CI workflows to Depot-managed runners (#8205)
* [AI] Migrate CI workflows to Depot-managed runners

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Rename release notes to match PR number

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Empty commit to trigger CI

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Keep VRT jobs on GitHub-hosted runners

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Use 4-vCPU Depot Windows runners for Electron builds

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Use 4-vCPU Depot Ubuntu runners for Electron builds

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Use 4-vCPU Depot runners for functional e2e tests

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Scale Electron build runners to 8 vCPUs

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Scale Ubuntu Electron builds to 4 vCPUs and move Windows builds back to GitHub runners

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Move Microsoft Store publish back to GitHub Windows runner

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* [AI] Add actionlint config for Depot runner labels

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Matiss Janis Aboltins <MatissJanis@users.noreply.github.com>
2026-06-17 07:36:33 +00:00

55 lines
3.0 KiB
YAML

name: Fork PR Welcome
##########################################################################################
# WARNING! This workflow uses the 'pull_request_target' event. That means that it will #
# always run in the context of the main actualbudget/actual repo, even if the PR is from #
# a fork. This is necessary to get access to a GitHub token that can post a comment on #
# the PR. Be VERY CAREFUL about adding things to this workflow, since forks can inject #
# arbitrary code into their branch, and can pollute the artifacts we download. Arbitrary #
# code execution in this workflow could lead to a compromise of the main repo. #
##########################################################################################
# See: https://securitylab.github.com/research/github-actions-preventing-pwn-requests #
##########################################################################################
on:
# See banner above: posts a static welcome comment, no checkout,
# no PR-supplied script execution.
pull_request_target: # zizmor: ignore[dangerous-triggers]
types: [opened, reopened]
permissions:
pull-requests: write
jobs:
welcome:
name: Post Welcome Message
runs-on: depot-ubuntu-latest
if: github.event.pull_request.head.repo.full_name != github.repository
steps:
- name: Post welcome comment
uses: marocchino/sticky-pull-request-comment@0ea0beb66eb9baf113663a64ec522f60e49231c0 # v3.0.4
with:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
number: ${{ github.event.pull_request.number }}
header: fork-pr-welcome
hide_and_recreate: true
hide_classify: OUTDATED
message: |
<!-- fork-pr-welcome -->
👋 Hello contributor!
We would love to review your PR! Before we can do that, please make sure:
- ✅ All CI checks pass
- ✅ The PR is moved from draft to open (if applicable)
- ✅ The "[WIP]" prefix is removed from the PR title
- ✅ The PR description follows the provided template, with all checklist boxes filled in
- ✅ All CodeRabbit code review comments are resolved (if you disagree with anything - reply to the bot with your reasoning so we can read through it). The bot will eventually approve the PR.
- ✅ Any AI usage is disclosed (see our [AI Usage Policy](https://actualbudget.org/docs/contributing/ai-usage-policy))
A quick note on volume: please get one PR reviewed and merged before opening several more. A stack of simultaneous, similar PRs from one author is reviewed slowly, and low-effort, untested, or undisclosed-AI PRs may be closed without a detailed review.
We do this to reduce the TOIL the core contributor team has to go through for each PR and to allow for speedy reviews and merges.
For more information, please see our [Contributing Guide](https://actualbudget.org/docs/contributing/).