A historical recommendation engine for daily pair rotation management, with an interactive visual aide of each pairing team. Visit the app: https://parrit.io/
A CI-pipeline hosted instance that you can use!
A note from our dev team about why we've made this dramatic change
We publish our CI test runs to this site for easy viewing
- Remix.run
- React
- Xata.io
- Netlify
- Sentry (for bug detection)
- Playwright (e2e tests)
- GithubActions (general automation)
- Screenshots of test runs are published to our github pages site
- Detailed run success/failure information can be found in each task execution action ref
Big shoutout to the following people for helping to guide the direction that Parrit took. Core contributors also please feel free to add others to the core contributor list for those who significantly shape the direction of Parrit.
- Anthony Dreessen - Product Owner, Product Management + Full-stack Development
- Darcie Fitzpatrick - Product Design, Product Management + User Research
- Cat Zhang - Product Management + Product Design
- Joseph Greubel - Front-end Development, Back-end Development
- Michael Oleske - Back-end Development
Take a look at the tech talk we presented about the making of Parrit: https://youtu.be/YVMuMK5Ru_A
We use Xata as our data backend. Why? Because AI recommended it.
npm install -g @xata.io/clixata auth login
In order to connect to the core databases you'll need to be part of the Parrit Xata team. Reach out if you aren't already. You can also get started with your own Xata database for free.
Xata doesn't appear to have a clean way of migrating (or even exporting) the schema. What it does do is allow you to upload CSVs which become tables. Reach out for starter data or make some of your own.
easiest way is through the Xata UI
id: -1, project: null
- Install the Netlify CLI:
npm i -g netlify-cliIf you have previously installed the Netlify CLI, you should update it to the latest version:
npm i -g netlify-cli@latest- Sign up and log in to Netlify:
netlify login- Run the development server
netlify devOpen up http://localhost:8888, and you're ready to go!
That really should be all it takes to get up and running if you've been added to the correct accounts. If that doesn't work, contact AJ
To serve your site locally in a production-like environment, run
netlify serveYour site will be available at http://localhost:8888. Note that it will not auto-reload when you make changes.
We have Netlify deploys automatically set up through github workflow. Deploying to a branch should get you a preview environment. Deploying to main should deploy the production site.
if Netlify deploys break, you can try to recreate the error locally using these commands
# preview deployment
netlify deploy --build
# production deployment
netlify deploy --build --prod