singuliere b536b65189 GetFeeds must always discard actions with dangling repo_id (#19598) ... * GetFeeds must always discard actions with dangling repo_id See https://discourse.gitea.io/t/blank-page-after-login/5051/12 for a panic in 1.16.6. * add comment to explain the dangling ID in the fixture * loadRepoOwner must not attempt to use a nil action.Repo * make fmt Co-authored-by: Loïc Dachary <loic@dachary.org>		2022-05-05 11:39:26 -04:00
..
access_token.yml
access.yml
action.yml	GetFeeds must always discard actions with dangling repo_id (#19598)	2022-05-05 11:39:26 -04:00
attachment.yml
collaboration.yml
comment.yml
commit_status_index.yml
commit_status.yml
deleted_branch.yml
deploy_key.yml
email_address.yml
external_login_user.yml
follow.yml
foreign_reference.yml
gpg_key_import.yml
gpg_key.yml
hook_task.yml
issue_assignees.yml
issue_index.yml
issue_label.yml
issue_user.yml
issue_watch.yml
issue.yml
label.yml
login_source.yml
milestone.yml
notice.yml
notification.yml
oauth2_application.yml
oauth2_authorization_code.yml
oauth2_grant.yml
org_user.yml
project_board.yml
project_issue.yml
project.yml
protected_branch.yml
public_key.yml
pull_request.yml
reaction.yml
release.yml
renamed_branch.yml
repo_archiver.yml
repo_indexer_status.yml
repo_redirect.yml
repo_topic.yml
repo_transfer.yml
repo_unit.yml
repository.yml
review.yml
star.yml
stopwatch.yml
team_repo.yml
team_unit.yml
team_user.yml
team.yml
topic.yml
tracked_time.yml
two_factor.yml
user_open_id.yml
user_redirect.yml
user.yml
watch.yml
webauthn_credential.yml
webhook.yml