-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
GetFeeds must always discard actions with dangling repo_id (#19598) #19629
Merged
6543
merged 2 commits into
go-gitea:release/v1.16
from
singuliere:wip-backport-action-19598
May 8, 2022
Merged
GetFeeds must always discard actions with dangling repo_id (#19598) #19629
6543
merged 2 commits into
go-gitea:release/v1.16
from
singuliere:wip-backport-action-19598
May 8, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…19598) Co-authored-by: Loïc Dachary <loic@dachary.org> (cherry picked from commit b536b65) Conflicts: models/action_test.go The GetFeeds function does not have a Context argument in 1.16. models/action.go The SQL statement is essentially the same in 1.16 but structured differently. The Join() was copied and the created_unix field prefixed with `action`. models/action_list.go in 1.16 the loadRepoOwner method did not exist and it was done in the RetrieveFeeds method of web/feed/profile.go. The safeguard to skip when act.Repo == nil was moved there.
singuliere
force-pushed
the
wip-backport-action-19598
branch
from
May 6, 2022 07:51
32b4256
to
87241d5
Compare
singuliere
changed the title
GetFeeds must always discard actions with dangling repo_id (#19598)
Draft: GetFeeds must always discard actions with dangling repo_id (#19598)
May 6, 2022
singuliere
changed the title
Draft: GetFeeds must always discard actions with dangling repo_id (#19598)
GetFeeds must always discard actions with dangling repo_id (#19598)
May 6, 2022
zeripath
reviewed
May 6, 2022
GiteaBot
added
the
lgtm/need 2
This PR needs two approvals by maintainers to be considered for merging.
label
May 6, 2022
zeripath
approved these changes
May 6, 2022
GiteaBot
added
lgtm/need 1
This PR needs approval from one additional maintainer to be merged.
and removed
lgtm/need 2
This PR needs two approvals by maintainers to be considered for merging.
labels
May 6, 2022
6543
approved these changes
May 7, 2022
GiteaBot
added
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
and removed
lgtm/need 1
This PR needs approval from one additional maintainer to be merged.
labels
May 7, 2022
@singuliere please update branch |
make l-g-t-m work |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #19598
Fix #19631