Do we need to implement a CI/CD with GitHub Actions?

[airvzxf]

Disclaimer: Firstly, I want to mention that all of this writing is from my perspective, trying to contribute to your open-source project. I am from Mexico, and I speak Spanish, natively. Moreover, I have been speaking English for 8 years at work (I lived for 3 years in Columbus, Ohio).

Regarding discussion #274.

Although, what I should really do is bump it to Ubuntu 20.04 since the "Standard Support" for 18.04 ended last year.

I wonder if it is necessary to add a CI/CD (Continuous Integration/Continuous Release) taking advantage of the benefits of GitHub Actions. Although, again, I don't know the context of why Ubuntu 20.04 is not used. In my experience, I could assume that it may be due to issues of uncertainty about whether it is going to compile in this new version of Ubuntu or some related issues.

I've been reviewing the code very superficially, and these are my remarks regarding whether there are pros or cons to adding a CI/CD.

• Cons: There is a folder with unit tests, but the last update was one and a half years ago. Therefore, it is not feasible to do a CI/CD, since the unit tasks are not being updated and there is no certainty whether the application will work or not.
• Pros: You can create a cross-matrix of operating systems managed by GitHub (Standard GitHub-hosted runners for Public repositories). This could help to check whether it fails or not. Furthermore, also this matrix can use Docker and do it virtually as it is done at the moment.
• Cons: A release is not being done with binaries; this code is downloaded to the user's machine and compiled to generate the binary file, documentation, etc. I noticed that Arch Linux is using the source generated from your tag to download and build the binary, as this GitHub document shows: Source code archive URLs.

Finally, I don't have a strong opinion regarding the application or not for the CI/CD for your project.