Skip to content

Conversation

jmtd
Copy link
Member

@jmtd jmtd commented Aug 28, 2025

A quality-of-life action for managing PRs. If it works :)

@jmtd jmtd requested a review from jerboaa August 28, 2025 12:38
@jmtd
Copy link
Member Author

jmtd commented Aug 28, 2025

I need a review (from someone other than me) to merge. I can't verify this will actualy work, I think, until we merge it. If I raise the PR from a fork, then the new workflow is triggered for the PR, but it won't have write permission to the PR body from the main repository (since it's from the fork). See #598 for an example of that. But if I raise it from a branch in the same repo (as here), for reasons unknown the new workflow is not picked up.

@jerboaa
Copy link
Contributor

jerboaa commented Aug 28, 2025

Would you be able to create a PR on your fork based on this branch and see it in action? I'd like to have some sanity checked before merging this.

Also: add branch labels (e.g. ubi9)

Signed-off-by: Jonathan Dowland <[email protected]>
@jmtd jmtd force-pushed the gha-label-issues-no-jira branch from 39e3af0 to 88fe6a2 Compare September 2, 2025 15:49
@jmtd
Copy link
Member Author

jmtd commented Sep 2, 2025

@jerboaa
Here we go! This is the same file, but not the exact same commit (I've deleted the other workflows in my fork's ubi9 branch, otherwise I was scheduling all the container builds in my fork for every iteration on this)
jmtd#6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants