Skip to content

Conversation

EyeCantCU
Copy link
Contributor

Adds an entry to recipe.yml enabling users to define their own public keys for the 'verify' action

@EyeCantCU EyeCantCU requested a review from castrojo as a code owner January 3, 2024 22:01
@xynydev
Copy link
Member

xynydev commented Jan 9, 2024

This feature desperately needs documentation somewhere. I'm not sure about a new top-level recipe entry, though... I mean, I can see the point, I'm just hesitant. But idk if this is still the better alternative to recommending the editing of build.yml.

Ok, how about making this an optional parameter, which uses the ublue key if nonexistant? So that people who ignore changes when doing manual merges to the recipe won't get a broken build. Then include this option in the recipe commented-out with a short explanation. This should also be added to the docs here: https://github.com/ublue-os/startingpoint/tree/template/config#basic-options

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