github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 20:23:07 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #6657] Add GitHub workflow to welcome fork PR contributors #6653

New Issue
Closed
opened 2026-02-28 21:31:06 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:31:06 -06:00
Owner
Copy Link

Original Pull Request: https://github.com/actualbudget/actual/pull/6657

State: closed
Merged: Yes

This PR adds a new GitHub Actions workflow that automatically posts a welcome message on all pull requests coming from forks.

What it does

The workflow posts a friendly message to fork PRs with a checklist of requirements before the PR can be reviewed:

  • All CI checks pass
  • PR moved from draft to open
  • "[WIP]" prefix removed from title
  • All CodeRabbit review comments resolved

This helps reduce TOIL for the core contributor team and enables faster reviews by ensuring PRs are ready before maintainers spend time on them.

Security

The workflow uses pull_request_target to run in the base repository context (required to comment on fork PRs), but it's secure because:

  • ✅ No code checkout from forks
  • ✅ Only posts a static, hardcoded message
  • ✅ Minimal permissions (pull-requests: write only)
  • ✅ Uses pinned action versions

The workflow only runs for fork PRs (not same-repo PRs) and includes appropriate security warnings.

**Original Pull Request:** https://github.com/actualbudget/actual/pull/6657 **State:** closed **Merged:** Yes --- This PR adds a new GitHub Actions workflow that automatically posts a welcome message on all pull requests coming from forks. ## What it does The workflow posts a friendly message to fork PRs with a checklist of requirements before the PR can be reviewed: - All CI checks pass - PR moved from draft to open - "[WIP]" prefix removed from title - All CodeRabbit review comments resolved This helps reduce TOIL for the core contributor team and enables faster reviews by ensuring PRs are ready before maintainers spend time on them. ## Security The workflow uses `pull_request_target` to run in the base repository context (required to comment on fork PRs), but it's secure because: - ✅ No code checkout from forks - ✅ Only posts a static, hardcoded message - ✅ Minimal permissions (pull-requests: write only) - ✅ Uses pinned action versions The workflow only runs for fork PRs (not same-repo PRs) and includes appropriate security warnings.
GiteaMirror added the pull-request label 2026-02-28 21:31:06 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#6653
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?