- DONE - Get boltServer.ts working on a remote host
- DONE - Update boltServer to be calling the same functions as the expressServer
- DONE - Change Slack settings in Prod so that it calls the actual boltServer, not localhost
- DONE - Split out bot responses so they can get individual reactions
- Add in aggregated counts under each review, e.g. @Alex has done great blah blah blah emoji emoji (5 commits)
- Add in files touched and lines changed to the aggregate counts, e.g. @Alex has done great blah blah blah emoji emoji (5 commits, 25 files, +100 net lines)
- Add in PR count to the aggregate counts
- Update the CommitSummary type across the repo add in a branch:string value Nest an object of all the github standardized info where we can use github terminology where it's defined, see this comment for details: #11 (comment)
- Move the serverPath that currently lives in frontend/src/App.tsx into an env file
- Get Tailwind working on the App.tsx page and make it pretty
- Give the FE a more clear way of indicating that a request is being processed
- Add another input box to the FE App that lets you specific a number. Pass that number all the way through as the maxAgeHrs value.
- Work out how to get approved private repos showing in responses from GraphQL. Current query is efficient but omits private repos (even when a project owner is allowing OAuth scraping)
- Longer term but much bigger execise: Migrate from OAuth to a Github App. More details here. Until this happens, the tool will only see: public repos, and private repos of orgs that have not blocked OAuth access to their private repos read more on this.
- Use main branch on Render, not experimental
- Tidy up /server/slack files - currently lots of obsolete commentcode
- Work out why Render sometimes complains about the PORT allocation and takes a while to deploy
Almost everything that matters for now is in here.
Lightweight web app for interacting with server, especially in dev/local environment.
Adventures for another day.
==================
cd /frontend
npm install
npm run dev
and open up Vite localhost, and then for the server...
cd /server
bun --watch expressServer.ts
E.g. to test getCommits:
cd /server
bun cli.ts getCommits
etc
See /server/cli.ts
for all options
Tool comes from https://just.systems/
==================
Sample API response from Github:
{
"sha": "abcdef1234567890 - Unique identifier for the commit",
"commit": {
"author": {
"name": "Name of the author",
"email": "[email protected]",
"date": "2024-06-28T10:00:00Z"
},
"committer": {
"name": "Name of the Committer",
"email": "[email protected]",
"date": "2024-06-28T10:00:00Z"
},
"message": "Commit message describing changes",
"tree": {
"sha": "treeSHA1234567890-SHA-of-tree-object-associated-with-commit"
},
"url": "https://api.github.com/repos/yourusername/repository/commits/abcdef1234567890/url-to-view-commit-on-github",
"moreFieldsMayExistHere": "more-information-like-parents-verification-details-etc"
}
}