WIP: [FEAT] implement F3 support #57
Labels
No labels
arch
amd64
arch
arm6
arch
arm64
arch
arm7
arch
riscv64
backport/v1.19
backport/v1.20
backport/v1.21/forgejo
backport/v7.0/forgejo
backport/v8.0/forgejo
breaking
bug
bug
confirmed
bug
duplicate
bug
needs-more-info
bug
new-report
bug
reported-upstream
codeberg
database
CockroachDB
database
MySQL
database
PostgreSQL
database
SQLite
dependency-upgrade
dependency
ACT
dependency
alpine
dependency
asciinema-player
dependency
bleve
dependency
cache
dependency
certmagic
dependency
chart.js
dependency
Chi
dependency
Chroma
dependency
citation.js
dependency
codespell
dependency
css-loader
dependency
devcontainers
dependency
dropzone
dependency
editorconfig-checker
dependency
elasticsearch
dependency
enmime
dependency
F3
dependency
ForgeFed
dependency
garage
dependency
Git
dependency
git-backporting
dependency
Gitea
dependency
gitignore
dependency
go-ap
dependency
go-enry
dependency
go-gitlab
dependency
Go-org
dependency
go-rpmutils
dependency
go-sql-driver mysql
dependency
go-swagger
dependency
go-version
dependency
go-webauthn
dependency
gocron
dependency
Golang
dependency
goldmark
dependency
goquery
dependency
Goth
dependency
grpc-go
dependency
happy-dom
dependency
Helm
dependency
image-spec
dependency
jsonschema
dependency
KaTeX
dependency
lint
dependency
MariaDB
dependency
Mermaid
dependency
minio-go
dependency
misspell
dependency
Monaco
dependency
PDFobject
dependency
playwright
dependency
postcss
dependency
postcss-plugins
dependency
pprof
dependency
prometheus client_golang
dependency
protobuf
dependency
relative-time-element
dependency
renovate
dependency
reply
dependency
ssh
dependency
swagger-ui
dependency
tailwind
dependency
temporal-polyfill
dependency
terminal-to-html
dependency
tests-only
dependency
text-expander-element
dependency
urfave
dependency
vfsgen
dependency
vite
dependency
Woodpecker CI
dependency
x tools
dependency
XORM
Discussion
duplicate
enhancement/feature
forgejo/accessibility
forgejo/actions
forgejo/api
forgejo/branding
forgejo/ci
forgejo/documentation
forgejo/email
forgejo/federation
forgejo/furnace cleanup
forgejo/internationalization
forgejo/moderation
forgejo/privacy
forgejo/release
forgejo/scaling
forgejo/security
forgejo/ui
Gain
High
Gain
Nice to have
Gain
Undefined
Gain
Very High
good first issue
issue
closed
issue
do-not-exist-yet
issue
open
manual test
Manually tested during feature freeze
OS
FreeBSD
OS
Linux
OS
MacOS
OS
Windows
regression
release blocker
Release Cycle
Feature Freeze
release-blocker
v7.0
release-blocker
v7.0.1
release-blocker
v7.0.2
release-blocker
v7.0.3
release-blocker
v7.0.4
release-blocker
v8.0.0
run-end-to-end-tests
test
manual
test
needed
test
needs-help
test
not-needed
test
present
untested
valuable code
worth a release-note
User Research - Accessibility
User Research - bug
User Research - Config (instance)
User Research - Dashboard
User Research - documentation
User Research - Errors
User Research - feature
User Research - federation
User Research - Filters
User Research - governance
User Research - Labels
User Research - Moderation
User Research - Needs Input
User Research - Notifications
User Research - release
User Research - Repo creation
User Research - Repo Units
User Research - security
User Research - Settings (in-app)
User Research - testing
User Research - UI
User Research - UX
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: forgejo/forgejo#57
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I would like to work on an integration of F3 in Forgejo. I've done work a few months ago but the PR in Gitea went stale, in part because I did not have time to spend on it.
Given the recent developments of the Gitea project, I would prefer to work on Forgejo. F3 is useful in the context of forge federation and I'm looking forward to cooperate with developers who are actively working on it in Forgejo.
I accepted, I pledge to maintain and backport the forgejo-f3 branch to stable versions and rebase it as explained in the contribution guide.
advocacy for a forgejo-f3 branchto [FEAT] advocacy for a forgejo-f3 branchA a co-author of https://lab.forgefriends.org/friendlyforgeformat/gof3 I'm (obviously) in favor of creating such a branch. I pledge to also help maintain it.
I suggest to at least wait for a stable release (and the announcement?) before work here starts.
[FEAT] advocacy for a forgejo-f3 branchto [FEAT] implement F3 support@Ryuno-Ki I agree that it would be premature to backport anything to v1.18. But what about starting the work on v1.19?
I mean, if you have the capacity, go for it.
I could imagine, however, that after the v1.18 release, the holidays will cause most of the people to take a break from coding and spend time with family.
That would lead to a break in context, which might make it harder to catch up with what was written before christmas.
Therefore I suggested to wait a little.
I do. I'll start working in my own branch while the discussion continues.
Is this completed?
It was apparently closed because of a reference in the commits, re-opening.
The CI passes on the F3 branch, rebased on top of the
forgejo-developmentbranch. But it does not include the integration tests and they still fail. Working on it.It would be good to run integration tests (sqlite at the minimum) in the CI.
[FEAT] implement F3 supportto WIP: [FEAT] implement F3 supportMarked as WIP: so that it is not closed by accident. There still is significant work to do before it can be merged.
Rebased on top of the current
forgejo-developmentbranch and the CI is green after the following changes.method signature changes
https://ci.codeberg.org/forgejo/forgejo/pipeline/130/7
Fixed with these changes.
make tidy
https://ci.codeberg.org/forgejo/forgejo/pipeline/131/9
Fixed with these changes.
This keeps being closed due to the
fixesannotation in9c21037cce😩😊 thanks for fixing my mistake.
Reopening as it's once again only closed by the Docs commit
Created a followup issue at #93 so this one ca be closed.