GitHub Actions or Circle CI?

[warengonzaga]

I'm thinking of ways to automate the following.

• Linting
• Testing
• Building
• Packaging
• Releasing

I want to solve these issues while making this project and will apply them to my existing projects.
Any suggestions?

[warengonzaga]

For the testing, well by default we are going to use ESLINT (#20).
We might automate this thing or add it to the package building using Parcel instead.

[jofftiquez]

we can just add it in the code first. Then just one line in the CI script. BTW it's better to use GitHub Actions IMO

[warengonzaga]

Let's try to build a basic workflow on GitHub Actions first. For me, let's figure out our workflow first so we can easily automate it.

[jofftiquez]

I can write the script for Github action @warengonzaga if you need help.

[warengonzaga]

I can write the script for Github action @warengonzaga if you need help.

Submit an open PR so we can review it and discuss it here. Make sure to mention this here or mention this discussion on your PR.

[princejoogie]

Linting is not for testing, just for the cleanup of code formats.

My bad, where should we put linting? or put linting first in the process?

linting is currently handled pre-commit with husky, we can also add running tests there. it's good to have only tested and linted files to be pushed in github

but ofc, setting up gh actions is still necessary

[angelofallars]

I think it would be best if we build something in GitHub Actions first as it's already integrated into GitHub. Then if necessary we can just transition to Circle CI. I have some experience in GitHub Actions too.

[warengonzaga]

I think it would be best if we build something in GitHub Actions first as it's already integrated into GitHub. Then if necessary we can just transition to Circle CI. I have some experience in GitHub Actions too.

as per voting, the majority of the team prefer the GitHub actions. Let's see if GH will work for us.