uses the newly added description filter that only autlinks, and renders
backticks, bold and italics.

Signed-off-by: oppiliappan <me@oppi.li>

this sanitizer only renders a tiny subset of markdown, to be used in
inline elements like PR titles and repo descriptions etc.

Signed-off-by: oppiliappan <me@oppi.li>

Signed-off-by: oppiliappan <me@oppi.li>

sqlite db still has `at_uri` column to easily use as reference

Signed-off-by: Seongmin Lee <boltlessengineer@proton.me>

Signed-off-by: Seongmin Lee <boltlessengineer@proton.me>

There is no reason for `ResolvedRepo` to not directly inherit `Repo`

Signed-off-by: Seongmin Lee <boltlessengineer@proton.me>

tailwind seems to apply this to every html element. when applying
font-mono to an element, it inherits the ss01 font feature. this results
in a different `a` characters from when inside `pre` and `code` blocks,
where it resets the list of font-features.

i can't seem to find a good fix for this issue. removing the ss01
feature altogether seems like a good fix, the number alternates in inter
aren't all that different in my opinion.

Signed-off-by: oppiliappan <me@oppi.li>

- remove redundant divs in base layout
- allow scrolling changed-files listing
- show more of the file in tree views
- unify repo-index and repo-tree views

Signed-off-by: oppiliappan <me@oppi.li>

Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>

Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>

Replace `Issue.IssueAt` to `Issue.Rkey`. `issue_at` column still exist,
but not used and will be removed in future.

Remove `db.SetIssueAt()` in flavor of `Rkey`.
Create rkey *before* adding to DB, and save same rkey to PDS.
This is safe as `tx` is will be dropped when `ctx` is canceled with
error.

Signed-off-by: Seongmin Lee <boltlessengineer@proton.me>

Otherwise, when programs create files in $HOME, others that check the Git
repo's state may be sad (or at least emit warnings in response to) it
being dirty.

Signed-off-by: Winter <winter@winter.cafe>

IMO, we shouldn't make errors opt-in to actually show upon push, at least
not if/until we have a UI to show them to the user.

Signed-off-by: Winter <winter@winter.cafe>

This moves away from the old method of creating a container with some
shared volumes to one that most users would expect: any changes made
in one step will be accessible by the following steps, and not only if
they're in the workspace or `/etc/nix`. This also paves the way for a
more generic Docker image engine, as users can do things like `apt install`
without the results being blown away across steps.

Signed-off-by: Winter <winter@winter.cafe>

It's possible for SetupWorkflow to provision resources and also fail, so
this makes sense for robustness.

Signed-off-by: Winter <winter@winter.cafe>

Signed-off-by: Winter <winter@winter.cafe>