forgejo/modules/migration
Jason Song e4eaa68a2b
Replace yaml.v2 with yaml.v3 (#21832)
I don't see why we have to use two versions of yaml. The difference
between the two versions has nothing to do with our usage.
2022-11-21 16:36:59 +08:00
..
file_format_testdata
schemas
comment.go Store the foreign ID of issues during migration (#18446) 2022-03-17 18:08:35 +01:00
downloader.go Store the foreign ID of issues during migration (#18446) 2022-03-17 18:08:35 +01:00
error.go
file_format.go Replace yaml.v2 with yaml.v3 (#21832) 2022-11-21 16:36:59 +08:00
file_format_test.go
issue.go Add more linters to improve code readability (#19989) 2022-06-20 12:02:49 +02:00
label.go
messenger.go
milestone.go
null_downloader.go Fix dump-repo git init, fix wrong error type for NullDownloader (#20182) 2022-07-01 07:48:25 +08:00
options.go
pullrequest.go Add more checks in migration code (#21011) 2022-09-04 13:47:56 +03:00
reaction.go
release.go Add more checks in migration code (#21011) 2022-09-04 13:47:56 +03:00
repo.go Add more checks in migration code (#21011) 2022-09-04 13:47:56 +03:00
retry_downloader.go Store the foreign ID of issues during migration (#18446) 2022-03-17 18:08:35 +01:00
review.go Prevent NPE whilst migrating if there is a team request review (#19855) 2022-06-09 10:50:05 +08:00
schemas_bindata.go Remove legacy +build: constraint (#19582) 2022-05-02 23:22:45 +08:00
schemas_dynamic.go Remove legacy +build: constraint (#19582) 2022-05-02 23:22:45 +08:00
schemas_static.go Remove legacy +build: constraint (#19582) 2022-05-02 23:22:45 +08:00
uploader.go