feat: add ci for prettier check and build

[kunal00000]

Added CI for prettier check and build on PRs and pushes.
Resolves #47

[marcelovicentegc]

Static tests could run on git hooks/pre-commits as well along with a linter 😄. What do you think?

[kunal00000]

I gave rebasing a shot, and I'm crossing my fingers that I got it right. 🧐 I always feel a bit on edge when I'm rebasing branches, especially when there are conflicts involved.

[steve8708]

apologies, we just merged a few more things, needs one more round of conflict resolution and then we can get this in!

[kunal00000]

@steve8708 resolved conflicts ✅

[marcelovicentegc]

@kunal00000, I see lots of overrides from changes that were already integrated to the main branch on this PR. It occurs to me that this might introduce some inconsistencies to the git history. Can you open a new PR including the prettier check? It will help us keep the repository and its git history clean 😄

[marcelovicentegc]

Also, here's a step by step to rebase and preserve the repo git history from a forked repo (adapted from https://stackoverflow.com/a/7244456/9317004)

# Add the remote, call it "upstream":

git remote add upstream git@github.com:BuilderIO/gpt-crawler.git

# Fetch all the branches of that remote into remote-tracking branches

git fetch upstream

# Make sure that you're on your main branch:

git checkout main

# Rewrite your master branch so that any commits of yours that
# aren't already in upstream/master are replayed on top of that
# other branch:

git rebase upstream/main 

[marcelovicentegc]

I'm leaving a suggestion to open a new PR including only the changes for the prettier check step on CI since this PR duplicates the git history (per #48 (comment))

[kunal00000]

Thanks @marcelovicentegc 🤠. created another PR for this.
Closing this one