fix(ssh): ssh help text formatting

chore: gitignore

feat: ability to delete repo

refactor: `--comment` flag is now a bool that reads from stdin for comment

Replaced `--comment` flag which was a string into a bool and now require comment to be provided by stdin for commands `accept`, `close`, and `reopen`.

`echo "lgtm!" | ssh pr.pico.sh pr accept --comment 100`

If no `--comment` flag provided then you don't need to provide stdin.

chore(docker): bump go

fix(ssh): remove last traces of charm/ssh

refactor(ssh): replace wish with pssh

chore: added changelog and version identifier

I'm using the date as the semver to make my life easier

refactor: require user to create an account

We have noticed that users are accidentally creating accounts because we automatically create an account for any operation.  So instead we are going to require a one-line remote cli command to register the account first we can help users figure out they are using the wrong pubkey.

fix: only admins, repo, and pr owners can change status

I'm not sure why I made it so anyone could change the status but it impacts where the PR goes in the UI which I thin k we want to be exclusive to contributors.

style: merge range diff details and patchset added timeline

style: timeline event display

style: tabbed layout for PRs

fix: add branch name to repo details

style: constrain pre boxes to the page

feat: show auth and commit info for range diff

chore: highlighting

chore: trying to diff only things that changed

chore: more granular diffs

chore(range-diff): more tests

chore: git src ignore

design: patchset tweaks

feat: range-diff tool

This tool enables anyone to quick paste their patches and have us
perform a range-diff on them

fix: runtime bugs while watching logs

fix: event data scan exception

chore: add comment e2e test

fix: linter

add comments to status changes

Signed-off-by: jolheiser <git@jolheiser.com>

strongly type event data

Signed-off-by: jolheiser <git@jolheiser.com>

strongly type status

Signed-off-by: jolheiser <git@jolheiser.com>

gofumpt and modernize

This is the result of running:
- gofumpt -> https://github.com/mvdan/gofumpt
- modernize -> https://pkg.go.dev/golang.org/x/tools/gopls/internal/analysis/modernize

Signed-off-by: jolheiser <git@jolheiser.com>

Add range-diff to contrib

Helpful to be able to see a valid range-diff when doing some dev testing.
As an example, this PR was originally intended for something else that turned out to be me testing range-diffs incorrectly. 😅

Signed-off-by: jolheiser <git@jolheiser.com>

refactor: restructure web assets

- Move component (non-page) assets into a components sub-directory
  - This makes parsing all of them simpler without needing to add to the list in-code
- Move pages into their own subdirectory
  - Allows simplifying their name and distinguishes which files are the "actual" pages
- Move parsing to vars
  - Cleans up some overhead by not having to parse the templates on *every* page load while also simplifying the callsite

Signed-off-by: jolheiser <git@jolheiser.com>

chore: makefile changes to support podman

single binary

Reduce web and ssh to a single binary called git-pr that runs both the SSH and web servers at the same time

Signed-off-by: jolheiser <git@jolheiser.com>

chore: don't render binaries as diffs

fix patchset count for specific user

Signed-off-by: jolheiser <git@jolheiser.com>

rename binaries

Rename the binaries to avoid any potential for "ssh" (or "web") binaries.
In particular, "ssh" could conflict with openssh and lead to confusing behavior.

Signed-off-by: jolheiser <git@jolheiser.com>

chore(cli): update description

chore: add comment for `desc` cfg

feat: allow config `desc` to add a description box to index page

refactor: consolidate docs page onto index

This change will allow maintainers to add a description box to the top
of their git-pr instance as an introduction to their service.

docs: copy

refactor(cli): replace `pr print` with `print`

chore(cli): remove `pr diff`

chore: copy

refactor: add docs page

refactor: reviews are not a pr status anymore

refactor: allow anyone to review or add patchsets to PR

Don't overlap ip addresses

docs: todo

design: show number of prs next to status filters

chore: fix colspan for pr-table

fix(range-diff): properly handle removed files from a patchset

refactor: better rendering of range diff for web

style: split diff view for range diff

chore: rm deprecated hungarian algo

fix(web): use correct templates to render

style: range-diff long-form patch descriptions

refactor: return range diff header

This will allow us to generate different outputs directly in our
templates using the RangeDiffHeader struct

style: range-diff sidebar

chore: fixes

feat: dedicated range-diff page

chore: sort range diff

refactor(web): default status is open

This changes the default patch request index view to show only patch
requests with status `open`.  This helps with the noise.

feat: filter links for pr-table

fix: highlight review patches

This was a regression from a previous refactor.  Now we show added
patches from a reviewer.

fix: user repo owner id for repo links

style: reset patchset list on mobile

style: tweaks

fix: better location for patch file anchor link

style: patch files collapsable

style: sticky diff headers and patchset list

style: make breadcrumbs consistent

chore: enforce foreign_key constraints

fix: single tenant doesnt require user namespace

chore: rm print line

fix: repo owners have full perms

feat: add multitenancy

The goal of this change is to support the ability to let any user create
repos, similar to popular code forges.  Repos are created adhoc when a
user uploads a patchset.

As part of this change, we are deprecating the previous way to configure
repos.  Repos can be thought of as containers for patch requests and not
much more.  They don't need to strictly map to a git repo.

Multitenancy is opt-in via the `git-pr.toml` field:

```
create_repo = "user"
```

style: wrap file links

style: pr detail

style: pr detail

style: smol classes

chore: cleanup templates

style: pr detail reorg

feat: ability to view all patchsets

feat: user-detail page

feat: sorting

feat: ability to filter pr table data by status, title, and user

refactor: table format for prs

refactor: separate models from sqlite db

We will likely want to support postgresql so this change will make that
easier.

feat: range diff

chore: update smol

feat: improve documentation

This improves documentation by stating the admin list needs to be
populated with ssh pubkeys and that the config file repos can be
configured with a default_branch name to show in the help text.

style: tweaks

style: update smol

chore: update `pr reopen` cmd as well

fix: log admin as closer

Previously the contributor was logged as the closer, even when an admin closed a pr

Signed-off-by: jolheiser <git@jolheiser.com>

fix(contrib.dev): linter

chore: gitignore `review.patch`

contrib: add dev script

This patch adds a fairly contained dev script that almost doubles as an integration test if you squint hard enough.
It runs an isolated instance that we can add more things to, it at least seems handy to me for quickly testing how changes affect e.g. the web UI, RSS feed, etc.

Signed-off-by: jolheiser <git@jolheiser.com>

fix: only log status change if the status changes

Signed-off-by: jolheiser <git@jolheiser.com>

fix: use eventlog time for pr details

Signed-off-by: jolheiser <git@jolheiser.com>

fix: insert repoID with pr creation

We need to add the repoID when a new pr is created.
As well, all NullXXX when inserting should be set to Valid.

Signed-off-by: jolheiser <git@jolheiser.com>

docs: readme

style(web): repo-list pr item

fix(cli.add): mark accept and close as reviews as well

feat(cli): add `--accept` and `--close` to `pr add` cmd

refactor(cli): always print PR summary when applicable

chore: rearrange pr status location

chore: fmt readme

style: color success pill

docs: fix typo / minor rewording in readme

refactor: create events within tx

feat: consistent user display

This patch unifies how user accounts look across the entire frontend
It also adds some CSS specifically for reviews/admins

Signed-off-by: jolheiser <git@jolheiser.com>

feat: static assets folder

Create a static folder that will be served as-is with the ability for
users to bring-their-own static folder.

If we detect `data_dir/static/` we will serve that instead of the
embedded one we provide by default.

fix(cli): access control for removing patchsets

I also fixed some other access control issues for changing PR status.

fix(db): re-add empty string

fix(cli): set correct patchset id when creating patch

fix(cli): remove vim comment

This was probably not a great solution and instead we should rely on the
end-user to figure out how to properly highlight in their editor

chore: better error handling for cfg and db

style: repo-detail separate commands

docs: show desc on repo detail pages

fix: use `git-pr.toml` as default source of config

docs(pr): add cli for patchset diff

feat: empty patch support

`git format-patch --cover-letter` is a great way to provide a summary
of all the changes within a patchset so we want to explicity support
that functionality.

The only gotcha here is we now allow empty patches.  So if there is an
empty patch in the patchset, the committer needs to add another option:
`git am -3 --empty=stop|drop|keep` depending on their preference.

chore: update `go-gitdiff`

chore: remove dead code

refactor: store patch author date as datetime

refactor: patch requests -> patchsets -> patches

Previously a patch request contained a series of patches.  This worked
great as an MVP but we are starting to see some issues with this impl.

Previously the contrib and reviewer would push patches to git-pr similar
to github pull requests.  They all get merged into a single patchset.
This mostly works until you want to start editing previous commits to
keep the commit history tidy and relevant.  For many workflows, going
back to a previous commit and amending it to address feedback is
desirable.

This creates a new model, patchset, which is a mostly immutable
container for patches.  1-to-many patch request to patchsets and
1-to-many patchset to patches.  Think of these patchsets as revisions.

This allows us to better organize collaboration and enable features like
`git range-diff` to see changes between revisions.

BREAKING CHANGE: sqlite dbs will have to be recreated as the new models
are fundamentally different. Sorry for the inconvenience!

fix: for content sha ignore diff file with base-commit

Our content sha computation is wrong when one contrib provides a
base-commit and the other does not.

Unfortunately this is dependent on the client and whether or not they
provide the base commit `git format-patch --base` so we have to hack
around it to keep commit sha identical.

content sha should ignore diff file with base-commit

Eric Bower (1):
  fix: for content sha ignore diff file with base-commit

 pr.go | 20 ++++++++++++++++++--
 1 file changed, 18 insertions(+), 2 deletions(-)

--
2.45.2

chore: rm favicon since we dont have one yet

feat: add basic OGP data to patch request page

This patch adds some basic OGP data to the patch request details page.
It includes the title, URL, and site name.

Signed-off-by: jolheiser <git@jolheiser.com>

fix: ensure repo exists before creating a patch

feat: list only your own PRs

Signed-off-by: jolheiser <git@jolheiser.com>

refactor: convert AuthorDate to time.Time then format with cfg

Unfortunately, `patch.AuthorDate` is stored as `TEXT` in sqlite and not
a `DATETIME` so we have to do extra work to convert it on-the-fly.

We can create a separate migration to convert it to a datetime.

feat: configurable time format

This patch allows the displayed time format to be configurable.
By default it uses time.RFC3339

Signed-off-by: jolheiser <git@jolheiser.com>

fix: use config url for web pages

This patch uses the config URL in the frontend so that self-hosted users can point contributors to use their SSH server.

Signed-off-by: jolheiser <git@jolheiser.com>

docs: readme

docs: readme

docs: readme

docs: readme

docs: add example flow using actual commands

chore: add license

refactor: move patch parsing code

chore(cli): desc order for ls commands

docs: copy

docs: copy

docs: readme

chore: cleanup

feat: show event log in pr detail web view

docs: readme

refactor: data -> data_dir

fix: data path

fix: use command override

refactor: docker

feat: config via toml

docs: readme

docs: readme

docs: readme logo

fix: add base_commit_sha to schema

style: pr item spacing

docs: readme

docs: readme

style(web): highlight admin

style(cli): add more info to lists

docs(readme): roadmap

refactor: repo list pr should use last updated pr

chore: add `git-pr` to list of repos

fix: rss

feat: record base commit if it exists

docs: copy

fix: upsert user

style: tweaks

chore: prevent user collisions

chore: use username instead of pubkey

docs: copy

feat: banned

feat: acl

refactor: user model

feat: acl

chore: cleanup

chore: db migrations

code passes

chore: cleanup

feat: ability to change PR title

chore: cleanup

fix: repo list

docs: copy

chore: move fns around

refactor: remove comments

I'd rather comments be part of a patch

feat: print patch request sub slice

chore: cleanup

style: light theme syntax

chore: change copy for submitting pr

fix: anchor links

refactor(pr-detail): combine pages

fix: print raw text without printf values

style: cleanup

style: sort by pr status

chore: pr status print success msg

feat: rss feeds

docs: add some explainer text

chore: more repos

chore: close -> closed

style: tweaks

feat: `pr add --force` to replace patchset

style: various design tweaks
feat: list repo ID with `pr ls`

chore: more repos

refactor: use templates

fix: contributors are allowed to close their own PRs

refactor

changes

refactor: split patchsets and calc content sha

chore: copy

fix: submit patch request exception

chore: cleanup web viewer

refactor: cleanup

chore: cleanup

refactor: compose files

chore: cleanup

chore: fix docker

web view

docs: readme

chore: fix compose file

chore: db changes

chore: changes

chore: docker prod

chore: docker

web server

change

docs

refactor: use urfav/cli

changes

progress

progress

tweaks

working

changes

changes

review

progress

changes

progress

progress

changes

nice

mostly working

changes

changes

exposition

sauce

prototype

chore: working on db models

progress

Wow does this actually work?

I wonder how we can do this.