Skip to content

Conversation

@amd-aliem
Copy link
Contributor

@amd-aliem amd-aliem commented Oct 24, 2025

Add option to specify a forked beacon repo. This will incorporate the latest release of that forked repo, instead of the default AMDEPYC one.

image

Add an option to the manual_dispatch trigger for forked beacon
repos. Useful for testing beacon changes.
@amd-aliem amd-aliem force-pushed the beacon-test-support branch from cc31f80 to 2008991 Compare October 24, 2025 20:09
@amd-aliem amd-aliem marked this pull request as ready for review October 24, 2025 20:10
@amd-aliem amd-aliem enabled auto-merge (rebase) October 24, 2025 20:10
Copy link
Contributor

@markg-github markg-github left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like there's a small conflict now, but this looks good, and useful.

@amd-aliem amd-aliem disabled auto-merge November 7, 2025 20:58
@amd-aliem amd-aliem marked this pull request as draft November 7, 2025 20:59
@amd-aliem
Copy link
Contributor Author

Converted to draft - some open questions from @DGonzalezVillal about how to prevent people from overwriting main devel release in this repository. Probably either need to make sure it's not executable in AMDEPYC repo, or make it change the release name to like devel-<fork name> or something.

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