github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Issue export #2796

New Issue
Closed
opened 2025-11-02 04:48:49 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 04:48:49 -06:00
Owner
Copy Link

Originally created by @a7hybnj2 on GitHub (Jan 22, 2019).

  • Gitea version (or commit ref): 1.5.2
  • Git version: 2.19.1
  • Operating system: freeBSD Jail
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite

Description

This is a question because I messed it up!

I have 2 versions of gitea running 1.4.0 and 1.5.2 and I have active repos in both. I need to migrate the repos from 1.4.0 -> 1.5.2 with the issues intact.

Yes - I could, and will if needed, go into each repo and manually copy all the issues over but I would like a way to export and import. Any help would be great!

Originally created by @a7hybnj2 on GitHub (Jan 22, 2019). - Gitea version (or commit ref): 1.5.2 - Git version: 2.19.1 - Operating system: freeBSD Jail - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite ## Description This is a question because I messed it up! I have 2 versions of gitea running 1.4.0 and 1.5.2 and I have active repos in both. I need to migrate the repos from 1.4.0 -> 1.5.2 with the **issues** intact. Yes - I could, and will if needed, go into each repo and manually copy all the issues over but I would like a way to export and import. Any help would be great!
GiteaMirror added the issue/duplicate label 2025-11-02 04:48:49 -06:00
GiteaMirror commented 2025-11-02 04:48:50 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 23, 2019):

duplicated with #4808

@lunny commented on GitHub (Jan 23, 2019): duplicated with #4808
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2796
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?