-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate version submittion thanks to Kodi addon submitter #41
Comments
@joaopa00 ? Would you be able to create an access token for the repo please ? https://docs.github.com/en/[email protected]/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens If so, I can try to add kodi addon submitter https://github.com/xbmc/kodi-addon-submitter . |
Ummm I do not understand what you mean. I have a personal token for all my github repos (personal and CUTVM) |
Sorry I made a shortcut. The GitHub action kodi submitter use this secret containing the token to auth and create the PR in kodi repo via GitHub API. |
Great ! I will try with this secret soon and keep you posted. |
Please note I also had to create a secret EMAIL to make the job work. |
Hello @joaopa00, Thank you for merging #44, but the build fail, because secret EMAIL is missing. See error message in logs https://github.com/Catch-up-TV-and-More/resource.images.catchuptvandmore/actions/runs/6541261959/job/17762519552 :
|
I think I have done. I will close this issue when we release a new version and if the bug is fixed. |
It is possible to use https://github.com/xbmc/kodi-addon-submitter in GitHub workflow in order to submit PR to official Kodi repository.
I plugged it in my addon for exampel : https://github.com/thomas-ernest/plugin.video.arteplussept/blob/master/.github/workflows/release-addon.yml#L10-L18
I also see this example : https://github.com/romanvm/kodi.tvmaze/blob/master/.github/workflows/publish-addon.yml#L35
There is a need to create a GitHub token (with a validity period) and set it as a secret in the current repo.
The text was updated successfully, but these errors were encountered: