-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Nest metadata in refactoring docs #23087
Conversation
Thank you. I just had some thoughts about that the refactoring guideline should be clarified about:
For example: Now 1.19 is releasing, if a refactoring PR is big, it should be done after 1.19.1, this will make bug fixes for 1.19.1 could be backported easily. Because only after 1.19.0 released, there are enough users to use and report bugs. If a big refactoring PR is merged into 1.20-dev before 1.19.1, then the backporting of bug fixes for 1.19.1 would cause many conflicts. |
Whitespace was missing from refactoring docs metadata. backport label applied so it is included in versioned docs.
* giteaofficial/main: Make issue meta dropdown support Enter, confirm before reloading (go-gitea#23014) Fix SyncOnCommit always return false in API of push_mirrors (go-gitea#23088) Fix commit name in Apply Patch page (go-gitea#23086) Add wrapper to author to avoid long name ui problem (go-gitea#23030) Avoid Hugo from adding quote to actions url (go-gitea#23097) Remove all package data after tests (go-gitea#22984) Change style to improve whitespaces trimming inside inline markdown code (go-gitea#23093) Nest metadata in refactoring docs (go-gitea#23087) # Conflicts: # templates/repo/issue/view_content/context_menu.tmpl
Whitespace was missing from refactoring docs metadata.
backport label applied so it is included in versioned docs.