loading...

Contributing assets is never easy, but we have GitHub Actions

outloudvi profile image Outvi V ・2 min read

Yeh, we have been building a site of soundbites for monthes.

https://suisei.moe/

Also yeh, collecting sound clips from videos is never easy. You need a good connection to YouTube. You need youtube-dl. You need ffmpeg. You also need to know how to use ffmpeg. And sure, many fans (whoever want to contribute to this project) are Windows users and they don't know about anything above. So how to do the audio collection?

Our idea is letting users contribute by simply commenting in a issue.

Procedure

  1. A contributor making comments.
  2. Our bot analyzes the comments, clip the audio and save it somewhere.
  3. Our bot replies the link to the contributor.

This is a solution enough for the problem. After that, the contributor just downloads the file, fills in the metadata and makes a pull request to our project... wait, pull request?

They are not used to the terminal and now you ask them to make a PR

🤔

Well... that's a problem. To ease the process, we need to avoid writing code for merely submitting an audio clip. This is where the GitHub action come:

A More User-friendly Procedure

  1. A contributor making comments.
  2. Our bot analyzes the comments, clip the audio and save it somewhere.
  3. Our bot replies the link to the contributor.
  4. An action detects the audio link.
  5. An action makes a PR with the audio link and the given metadata information.

That is our solution!

First, we tell the metadata:

Commenting on a issue

And finally, the PR is made:

Creating PR

Tada! 🎉

Last but not least, recently we rebuilt the site with Svelte 3, making it faster to view and easier to maintain.

Have a try on the brand-new ☄️https://suisei.moe!


This post, as well as this post, is a part of the GitHub Actions Hackerthon.

Posted on by:

outloudvi profile

Outvi V

@outloudvi

Student. Frontend developer. 0xa725cb57ca65cafe.

Discussion

pic
Editor guide