UnleashedRecomp icon indicating copy to clipboard operation
UnleashedRecomp copied to clipboard

GitHub Action doesn't respect Pull Requests and it's branches while validating.

Open AL2009man opened this issue 11 months ago • 3 comments

It appears that GitHub Action on the .yml validate doesn't include something like this:

on:
  pull_request:
    branches:
      - main
    types:
      - edited
      - opened
      - synchronize

While it's fine for releases, Git Actions will instead use main as opposed to using the pull request's changes for testing purposes.

This caused several hours of troubleshooting when trying to test the changes before merging to Master. Had to resort to building the file myself due to it.

AL2009man avatar Mar 11 '25 00:03 AL2009man

@AL2009man which of your PR's had this issue? For PR's that come from the outside only the yaml worklflow from main is used. So if your changes were there, then yes, they won't be taken into account. This is the workflow that fires for external PRs: https://github.com/hedge-dev/UnleashedRecomp/blob/main/.github/workflows/validate-external.yml

dcvz avatar Mar 11 '25 09:03 dcvz

@AL2009man which of your PR's had this issue? For PR's that come from the outside only the yaml worklflow from main is used. So if your changes were there, then yes, they won't be taken into account. This is the workflow that fires for external PRs: https://github.com/hedge-dev/UnleashedRecomp/blob/main/.github/workflows/validate-external.yml

Specifically, it's this one. https://github.com/hedge-dev/UnleashedRecomp/pull/1086 (and potentially the rest of my PR,)

Whenever GitHub Action files gets uploaded and be able to download it for testing, it doesn't seem to pick up my changes, at all. Meanwhile, my compiled build is able to pick up those changes no problem.

I've been trying to troubleshoot if it's something to do with my current fork repository (something got broken during the initial troubleshooting) or is this projects' way of doing PR Pulls isn't working.

AL2009man avatar Mar 11 '25 12:03 AL2009man

Why did you close? This is still a problem.

blueskythlikesclouds avatar Apr 07 '25 07:04 blueskythlikesclouds