-
-
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
Move almost all functions' parameter db.Engine to context.Context #19748
Conversation
fb7277d
to
c5cf75b
Compare
02b72c7
to
5240084
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Generally L-G-T-M. But I do not understand why some PRs have rebase + force-push after the reviews have started. In my mind, rebase + force-push only do harm to the project, it makes the review more difficult, and even worse it may lead to code lost. |
For me, that's because I'm also reviewing myself PR and found some code could be changed. Since Gitea asks to merge PR after updating, I have a habit to update the PR when possible to reduce the conflicts. |
But rebase doens't help about conflicts. A normal merge is enough for all cases, and the commit history is clear. In some cases, a normal merge doesn't trigger conflicts, but rebase does. Rebase seems worse than a normal merge in such cases. |
Please resolv conflict ;) |
make L-G-T-M work. |
* giteaofficial/main: Move almost all functions' parameter db.Engine to context.Context (go-gitea#19748)
…-gitea#19748) * Move almost all functions' parameter db.Engine to context.Context * remove some unnecessary wrap functions
As title.