feat: youtube to anchor workflow #805
Conversation
- Renamed action.yml to .action.yml.sample to reduce confusion. - Add the new YAML file to .github/workflows.
random video I found on youtube
- Filtered and copied the required files to .github/workflows. - Removed the video ID from episode.json to update later.
added "youtube-to-anchor-workflow" for testing purpose which can be removed later
AnimeshKumar923
requested review from
fmvilas,
quetzalliwrites and
derberg
as code owners
|
Hi there, please let us know if everything is working on the youtube to spotify GH action. We just fixed and released a new version of our GH action! Thanks for reporting the issue |
UPDATE
Detailed ReportWorkflow 1Workflow 2Workflow 3@derberg Please review and provide your feedback. I think the workflow is ready to be released. cc: Hey @akshatnema 👋 you can see the referenced issue and PR above for your analysis. 😉 |
Changes: - Changed the steps to match the newer version of the workflow.
|
Updated the documentation to match the latest version of the workflow. Can I add these steps as optional/additional at the end of the documentation? 👀
|
|
@AnimeshKumar923 yes, at the end, separate section, marked somehow it is optional @thulieblack from my side it is ready. Is there anything that you need? are instructions clear for you? |
Got it! |
|
Well done @AnimeshKumar923 this looks amazing. |
Thank you for your precious review @thulieblack 🙏 |
|
I was thinking of adding these points to the document. Could you please give some suggestions on it? |
Changes: - Added a section for additional steps after the upload of the podcast if finished. Co-authored-by: Lukasz Gornicki <[email protected]>
UPDATE |
|
Super cool @AnimeshKumar923 @thulieblack once merged, feel free to test in production 😄 /rtm |
Thank you so much! 🙇 @derberg |
|
I am testing the workflow; please let me know what is missing |
|
@thulieblack sorry, forgot to setup secrets for the workflow. Please try again |
|
@thulieblack we had an issue since 2 days as Spotify changed some labels in the signing page: Schroedinger-Hat/youtube-to-anchorfm#104 We've just merged the fix and created a new release. I think you can try a re-run of the workflow by taking the last action version, thanks |
|
@AnimeshKumar923 would it be fine to ask you to open a followup PR to use latest version of action? |
Will do 🫡 |
|
Description
Hey @derberg 👋
I've worked on this issue and got some progress. You can check that here: https://github.com/AnimeshKumar923/asyncapi-community/tree/youtube-to-anchor-workflow
I've also written a documentation which can be accessed here: https://github.com/AnimeshKumar923/asyncapi-community/tree/documentation-on-using-yt-to-anchor-action#note-this-documentation-section-will-remain-only-in-this-forked-repository-and-will-not-be-added-to-main-repository-without-discussing-it-with-the-maintainers
Link to original github action repository: https://github.com/Schrodinger-Hat/youtube-to-anchorfm
Since I didn't have any other ideas as where to add the documentation, I've changed the README.md of the asyncapi/community and put it in a separate branch so that it doesn't get merged with this PR.
We can discuss where to add the documentation and future scope of this feature either here or slack or zoom or google meet or where you're comfortable. 😄
Testing
It can be somewhat confusing so I'm adding the following:
For the testing the workflow, I propose these steps:
Read documentation from here: https://github.com/AnimeshKumar923/asyncapi-community/tree/documentation-on-using-yt-to-anchor-action#this-documentation-section-will-remain-only-in-this-forked-repository-and-will-not-be-added-to-main-httpsgithubcomasyncapicommunity-repository-without-discussing-it-with-the-maintainers
Follow this section of the documentation for testing: https://github.com/AnimeshKumar923/asyncapi-community/tree/documentation-on-using-yt-to-anchor-action#how-you-can-test-this
We can discuss about this after the
first yt-to-anchor automationpart as it requires testing with WhisperAPI which is now on paid subscription and as a student from 'not-so-good' financial background, I can't afford that part to test and integrate. Would require your support if it happens in future. 🙏Edit: I'm still not sure about the automation part of "extracting youtube video ID and putting it to
episode.json". Would require help on that part @thulieblack @AceTheCreatorLooking forward to hearing from you @derberg @thulieblack @KhudaDad414 @fmvilas
Related issue(s)
Partially Fixes #621