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 #6420] Fix VRT comment posting for fork PRs #6511

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

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

State: closed
Merged: Yes

Summary

This PR fixes the issue where VRT failure comments were not being posted on PRs from fork repositories.

Problem

The current implementation in e2e-test.yml tries to post comments directly using actions/github-script, but this fails for fork PRs because the GITHUB_TOKEN has read-only permissions for security reasons.

Solution

Use a workflow_run triggered workflow that runs with elevated permissions in the base repository context:

  1. Modified e2e-test.yml: Instead of posting comments directly, the workflow now uploads PR metadata (PR number, VRT result, artifact URL) as an artifact.

  2. New e2e-vrt-comment.yml: A new workflow that:

    • Triggers on workflow_run completion of "E2E Tests"
    • Has pull-requests: write permission
    • Downloads the metadata artifact
    • Posts a comment with the VRT report link if tests failed

This follows the same pattern already used in vrt-update-apply.yml for handling fork PRs safely.

**Original Pull Request:** https://github.com/actualbudget/actual/pull/6420 **State:** closed **Merged:** Yes --- ## Summary This PR fixes the issue where VRT failure comments were not being posted on PRs from fork repositories. ## Problem The current implementation in `e2e-test.yml` tries to post comments directly using `actions/github-script`, but this fails for fork PRs because the `GITHUB_TOKEN` has read-only permissions for security reasons. ## Solution Use a `workflow_run` triggered workflow that runs with elevated permissions in the base repository context: 1. **Modified `e2e-test.yml`**: Instead of posting comments directly, the workflow now uploads PR metadata (PR number, VRT result, artifact URL) as an artifact. 2. **New `e2e-vrt-comment.yml`**: A new workflow that: - Triggers on `workflow_run` completion of "E2E Tests" - Has `pull-requests: write` permission - Downloads the metadata artifact - Posts a comment with the VRT report link if tests failed This follows the same pattern already used in `vrt-update-apply.yml` for handling fork PRs safely.
GiteaMirror added the pull-request label 2026-02-28 21:29:22 -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#6511
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?