Closed mojavelinux closed 9 months ago
spiffy!
We just need to get the UI release process to work now so we can switch over to the UI bundle from this project.
Can you create a personal access token for webtide that has the "repo" scope (no other scopes needed), then navigate to https://github.com/webtide/jetty.website/settings/secrets/actions and create a repository secret named RELEASE_TOKEN
and paste in that value? That will allow the script to create tags and releases via the REST API. After that, I'll kick off the UI release again and switch to it when it's up.
done....I think.
It needed to be a classic token right?
-- Jesse McConnell - @.***> - CEO http://webtide.com - advice, and support for jetty and cometd
On Wed, Nov 22, 2023 at 2:27 PM Dan Allen @.***> wrote:
We just need to get the UI release process to work now so we can switch over to the UI bundle from this project.
Can you create a personal access token for webtide that has the "repo" scope (no other scopes needed), then navigate to https://github.com/webtide/jetty.website/settings/secrets/actions and create a repository secret named RELEASE_TOKEN and paste in that value? That will allow the script to create tags and releases via the REST API. After that, I'll kick off the UI release again and switch to it when it's up.
— Reply to this email directly, view it on GitHub https://github.com/webtide/jetty.website/pull/1#issuecomment-1823463520, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACCXL7EO2NH5HN74HSZJKTYFZN2LAVCNFSM6AAAAAA7VJFEGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRTGQ3DGNJSGA . You are receiving this because you modified the open/close state.Message ID: @.***>
For now, yes, a classic token. I'm sure there's a way to use the new token, but I don't yet have experience with it.