Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Forgejo Support #866

Open
2 of 10 tasks
lachmanfrantisek opened this issue Oct 24, 2024 · 1 comment
Open
2 of 10 tasks

Forgejo Support #866

lachmanfrantisek opened this issue Oct 24, 2024 · 1 comment
Labels
area/forgejo complexity/epic Lost of work ahead, planning/design required.

Comments

@lachmanfrantisek
Copy link
Member

lachmanfrantisek commented Oct 24, 2024 •
edited by lbarcziova
Loading

Since there is a significant chance that Fedora will pick Forgejo as its forge of choice, let's be prepared and plan what it would take to support it in OGR.

Implementation:
@lachmanfrantisek lachmanfrantisek added the complexity/epic Lost of work ahead, planning/design required. label Oct 24, 2024
@lachmanfrantisek lachmanfrantisek mentioned this issue Oct 24, 2024
Closed
2 tasks
This was referenced Dec 17, 2024
Closed
Open
Open
Open
Open
Open
Open
Open
Open
@dcermak
Copy link

dcermak commented Jan 24, 2025

Just fyi, I've been using my autogenerated API wrapper from the openAPI spec for gitea: https://github.com/dcermak/py-gitea-opensuse-org. Creating something similar for forgejo should be possible and could theoretically be embedded in this repo directly.

@lbarcziova lbarcziova moved this from new to in-progress in Packit Kanban Board Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/forgejo complexity/epic Lost of work ahead, planning/design required.
Projects
Packit Kanban Board
Status: in-progress
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lachmanfrantisek @dcermak @lbarcziova