As once our lord and savior Terry A. Davis said, "An idiot admires complexity, a genius admires simplicity."
And, welp, that's what I just did with my github bot Automata.

v1

Automata v1 was a real mess. We were supposed to publish a next.js website, a jobs system to make our lives easier, and a large etc.

Now, I've been working on this for quite a while (about a year) and I felt like I wasn't going anywhere. So I just thought about it we could run the automation scripts on Github Actions, right?

So I got to work

And in 4 days I got the whole thing working. I'm really proud of it.

We send API requests to Github whenever we want to trigger a workflow, on demand, by using the webhook system and handling everything from there.
As a bonus I also added a command, so we could merge on a more controlled way, specially on larger PRs.

Unexpected bugs on prod just after the PR merge

There were some bugs on launch.

• I didn't have a start script nor a license (commit)
• I forgot to change some environment variable names on index.ts (commit)
• A day later, forgot to listen on the PORT environment variable (commit)
• Squash and merge by default (ended up regretting it, see below) (commit)
• I FORGOT TO CHECK IF THE COMMAND MENTIONED @SERNBOT (commit)

That last one was a real pain, as I detected the bug in production, on the most important PR of the week, if not the month: the website's move to starlight docs.

Conclusion

Wow, a project with good DevEx? SIGN ME UP!

PD: I created a next.js template with my preferred tech stack, make sure to check it out! link