-
Notifications
You must be signed in to change notification settings - Fork 0
Description
For instance: prodezarts.com
Benjamin_Loison/Improve_websites_thanks_to_open_source#18. Do not have this issue with Exact.
Same issue with https://codeberg.org/api/swagger#/issue/issueListIssues.
Establishing a workaround based on download everything seems to make sense.
As I do not find, even with DuckDuckGo and Google search engines, a solution to export repository issues. Let us try to import on my own Gitea instance. Maybe it is a Codeberg intended limitation.
Maybe incorrect scopes, as there are two interesting ones: issue
and repository
.
Is there a dedicated option in Gitea for importing from Forgejo instance? As it seems to be such one on Codeberg.
With above both scopes (they are both required), I am able to import from Codeberg to Codeberg and then there is no issue anymore searching prodezarts.com
for instance.
Are issue ids kept? I do not have this feeling at least with Improve_websites_thanks_to_open_source_issues/issues/300.
Description
For instance: Improve_websites_thanks_to_open_source/issues?q=github.com
+183
Gitea Version
Not read.
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Not read.
Database
None