gitcafe tracking issue

clo commented

2026-02-19 01:03:07 -08:00

Owner

this issue is to track what things i use from forgejo and my git workflows. not all of these would be blockers to me actually using gitcafe as my primary git server.

minimum requirements

ability to log in
repositories
- can explore file trees
- syntax highlighted code
- permalinks to lines
- permalinks to regions
- private repositories (no invites, just private to me)
- public repositories with list of collaborators with write access (like nix/config)
issues
- markdown description and comments
- labels with names, colors, and descriptions
git over ssh (i do not use git over http)
- configure my ssh auth/signing key in the ui
trivially hostable on a single domain through docker

extras

if all of these items were implemented, i theoretically wouldn't be able to tell the difference in the two git servers.

ability to log in
- passkey
- openid connect
cosmetic features
- profile picture upload
- profile bio, location, and pronouns
- repository description
- repository icons
- custom css
issues
- ~~milestones~~ not planned
- sorting the issue tab by label ~~and milestone~~
- assigning a user to an issue
- auto-close an issue by pushing a commit with resolves #xx in the description
merge request.
- running a ci action. currently i do this with forgejo actions and their runner. but all i need is the ability to run a set of commands in a docker container that can clone the repository
- markdown comments
- labels
  - exclusive labels
- "WIP: " prefix in the name to make it a "draft"
- commenting on top of a line of code
- (i do not use PR reviews on forgejo)
git over ssh
- display signed commits with a checkmark
- "deploy keys", aka adding ssh keys that can be used for push on specific repositories. i use this for certain LLM code where an AI model is sandboxed in a container that has network access and a restricted deploy key
- push restrictions. ban pushing to master unless the commit is signed.
  - ban pushing to master if the merge request for the commit has failing CI
push mirroring
use a postgres database (i've manually edited some updated_at fields so backlogged projects appear correctly in Explore)

migration paths

import from forgejo
- code
- issues
  - comments on issues
  - labels
  - milestones
- prs
import from github
- code
- issues
  - comments on issues
  - labels
  - milestones
- prs

this issue is to track what things i use from forgejo and my git workflows. not all of these would be blockers to me actually using gitcafe as my primary git server. ## minimum requirements - [x] ability to log in - repositories - [x] can explore file trees - [x] syntax highlighted code - [ ] permalinks to lines - [ ] permalinks to regions - [x] private repositories (no invites, just private to me) - [x] public repositories with list of collaborators with write access (like [nix/config](http://git.paperclover.net/nix/config)) - [x] issues - [x] markdown description and comments - [x] labels with names, colors, and descriptions - [x] git over ssh (i do not use git over http) - [x] configure my ssh auth/signing key in the ui - [x] trivially hostable on a single domain through docker ## extras if all of these items were implemented, i theoretically wouldn't be able to tell the difference in the two git servers. - ability to log in - [ ] passkey - [ ] openid connect - cosmetic features - [x] profile picture upload - [x] profile bio, location, and pronouns - [ ] repository description - [ ] repository icons - [ ] custom css - issues - ~~milestones~~ not planned - [ ] sorting the issue tab by label ~~and milestone~~ - [x] assigning a user to an issue - [ ] auto-close an issue by pushing a commit with `resolves #xx` in the description - [x] merge request. - [ ] running a ci action. currently i do this with forgejo actions and their runner. but all i need is the ability to run a set of commands in a docker container that can clone the repository - [x] markdown comments - [x] labels - [ ] exclusive labels - [ ] "WIP: " prefix in the name to make it a "draft" - [x] commenting on top of a line of code - (i do not use PR reviews on forgejo) - git over ssh - [x] display signed commits with a checkmark - [ ] "deploy keys", aka adding ssh keys that can be used for push on specific repositories. i use this for certain LLM code where an AI model is sandboxed in a container that has network access and a restricted deploy key - [x] push restrictions. ban pushing to master unless the commit is signed. - [ ] ban pushing to master if the merge request for the commit has failing CI - [ ] push mirroring - [x] use a postgres database (i've manually edited some updated_at fields so backlogged projects appear correctly in Explore) migration paths - [ ] import from forgejo - [ ] code - [ ] issues - [ ] comments on issues - [ ] labels - [ ] milestones - [ ] prs - [ ] import from github - [ ] code - [ ] issues - [ ] comments on issues - [ ] labels - [ ] milestones - [ ] prs