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.

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

Update gogs upgrade information #22777

Merged
merged 2 commits into from
Feb 6, 2023
Merged

Update gogs upgrade information #22777

merged 2 commits into from
Feb 6, 2023

Conversation

jolheiser
Copy link
Member

@jolheiser jolheiser commented Feb 6, 2023

It seems that migrating from Gogs 0.12.x and above may require more work as time goes on and the projects continue to diverge.

This PR updates the docs to make it more clear.

@jolheiser jolheiser added the type/docs This PR mainly updates/creates documentation label Feb 6, 2023
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. labels Feb 6, 2023
@techknowlogick techknowlogick added skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. and removed lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. labels Feb 6, 2023
@GiteaBot GiteaBot added the lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. label Feb 6, 2023
@wxiaoguang
Copy link
Contributor

wxiaoguang commented Feb 6, 2023

It's better to put some more feasible methods there (eg: adopt the git repositories directly), and suggest users do not (never) do the "difficult" migrations . Otherwise it might cause strange problems for Gitea in the future, and make Gitea developers frustrated to help with the strange problems.

@jolheiser
Copy link
Member Author

It's better to put some more feasible methods there, and suggest users do not do the "difficult" migrations (eg: adopt the git repositories directly).

I considered that, however there isn't a good page to direct to for adopting repositories, so I wasn't entirely sure if it was worth saying "adopt the repos instead" without also explaining how that works, etc.

@lunny lunny merged commit 361d807 into go-gitea:main Feb 6, 2023
@jolheiser jolheiser deleted the upgrade-gogs branch February 6, 2023 15:18
zjjhot added a commit to zjjhot/gitea that referenced this pull request Feb 7, 2023
* upstream/main:
  Fix restore repo bug, clarify the problem of ForeignIndex (go-gitea#22776)
  Grammar fix (go-gitea#22790)
  Use link in UI which returned a relative url but not html_url which contains an absolute url (go-gitea#21986)
  Add repo adoption to FAQ (go-gitea#22778)
  Use import of OCI structs (go-gitea#22765)
  Update gogs upgrade information (go-gitea#22777)
  Add CLI option tenant ID for oauth2 source (go-gitea#22769)
  Refactor legacy strange git operations (go-gitea#22756)
  Add Chef package registry (go-gitea#22554)
  use drone secrets for s3 config (go-gitea#22770)
  remove update language in ProfilePost (go-gitea#22748)
  Set PR for issue when load attributes for PRs (go-gitea#22766)
  Fix time to NotifyPullRequestSynchronized (go-gitea#22650)
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. type/docs This PR mainly updates/creates documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants