ci: don't use pull_request in guix-build.yml

[UdjinM6]

Issue being fixed or feature implemented

pull_request doesn't have enough permissions. Only works for a branch in the same repo e.g. https://github.com/UdjinM6/dash/actions/runs/19731863320.

#6951 follow-up

What was done?

How Has This Been Tested?

For a branch from a forked repo UdjinM6#24:
develop: https://github.com/UdjinM6/dash/actions/runs/19732188359?pr=24
this PR (develop in my repo updated with this patch): https://github.com/UdjinM6/dash/actions/runs/19732354343?pr=24

Breaking Changes

n/a

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

[coderabbitai]

Walkthrough

The GitHub Actions workflow configuration in .github/workflows/guix-build.yml was restructured to flatten the event trigger hierarchy. Previously, a nested pull_request block existed under on.pull_request_target with a types: [labeled] filter. This configuration was moved so the event type filter now applies directly to pull_request_target at the top level. The workflow logic, steps, and push trigger remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file with minimal structural reorganization
• No functional logic changes or behavioral impact
• Simple YAML hierarchy flattening

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: removing the pull_request trigger from guix-build.yml in favor of pull_request_target.
Description check	✅ Passed	The description is directly related to the changeset, explaining the permissions issue with pull_request and providing test results demonstrating the fix.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3b9c29d and 01336d8.

📒 Files selected for processing (1)

• .github/workflows/guix-build.yml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/guix-build.yml

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

✅ No Merge Conflicts Detected

This PR currently has no conflicts with other open PRs.

[DashCoreAutoGuix]

Guix Automation has began to build this PR tagged as v23.0.0-devpr7014.01336d8b. A new comment will be made when the image is pushed.

[DashCoreAutoGuix]

Guix Automation has completed; a release should be present here: https://github.com/dashpay/dash-dev-branches/releases/tag/v23.0.0-devpr7014.01336d8b. The image should be on dockerhub soon.

[PastaPastaPasta]

utACK 01336d8