ktaube

At the end of this message, I will ask you to do something. Please follow the "Explore, Plan, Code, Test" workflow when you start.

Explore

First, use parallel subagents to find and read all files that may be useful for implementing the ticket, either as examples or as edit targets. The subagents should return relevant file paths, and any other info that may be useful.

Plan

Next, think hard and write up a detailed implementation plan. Don't forget to include tests, lookbook components, and documentation. Use your judgement as to what is necessary, given the standards of this repo.

If there are things you are not sure about, use parallel subagents to do some web research. They should only return useful information, no noise.

ktaube

Please analyze the GitHub PR: $ARGUMENTS.

Follow these steps:

1. Use gh pr view to get the PR details and description
2. Use gh pr checkout to switch to the PR branch
3. Use gh pr diff to examine the changes
4. Analyze the codebase to understand the broader context
5. Think deeply about the big picture impact of these changes
6. Provide a high-level pseudocode summary that captures:

ktaube

@charset "UTF-8";
.pf-c-table, .pf-c-select, .pf-c-page__sidebar.pf-m-light, .pf-c-menu, .pf-c-masthead.pf-m-light-200, .pf-c-masthead.pf-m-light, .pf-c-input-group, .pf-c-form-control, .pf-c-data-list, .pf-c-context-selector__menu, .pf-c-chip-group, .pf-c-chip, .pf-c-calendar-month, .pf-c-banner.pf-m-warning, .pf-c-banner.pf-m-gold, .pf-c-banner.pf-m-info, .pf-c-banner.pf-m-blue, .pf-c-alert, .pf-c-accordion, .pf-t-light {
  --pf-global--Color--100: var(--pf-global--Color--dark-100);
  --pf-global--Color--200: var(--pf-global--Color--dark-200);
  --pf-global--BorderColor--100: var(--pf-global--BorderColor--dark-100);
  --pf-global--primary-color--100: var(--pf-global--primary-color--dark-100);
  --pf-global--link--Color: var(--pf-global--link--Color--dark);
  --pf-global--link--Color--hover: var(--pf-global--link--Color--dark--hover);
  --pf-global--BackgroundColor--100: var(--pf-global--BackgroundColor--light-100);
}

ktaube

#!/bin/sh

rm -f .venv-core
echo "Freezing core requirements..."
python3 -m venv .venv-core

./.venv-core/bin/pip install -r requirements.txt
./.venv-core/bin/pip freeze > requirements-freeze.txt
rm -rf .venv-core
echo "Done."

ktaube

The experience of using Node.JS with TypeScript, ts-node, and ESM is horrible.

There are countless guides of how to integrate them, but none of them seem to work.

Here's what worked for me.

Just add the following files and run npm run dev. You'll be good to go!

package.json

ktaube

! name: Linkedin profile goggle
! description: Find linkedin urls
! public: false
! author: Kristaps Taube
! avatar: #000000

/in/*$boost=3,site=linkedin.com
/company/*$boost=3,site=linkedin.com

$discard

ktaube

Brew Bundle Brewfile Tips

Copyright & License

Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.

Sponsor

If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.

ktaube

create table lists (
    id serial primary key,
    name text,
    created_at timestamptz default now(),
    -- user_id will come from the users db on hasura side
    user_id int
);

create table startup_lists (