72ee7f3b00
- Consider the following scenario: a private repository in an organization with a team that has no specific access to that repository. Members of that team are still able to visit the repository because of entries in the `access` table. - Consider this specific scenario for the gathering of issues for project tables. - Unit test added - Resolves forgejo/forgejo#7217 - Ref: forgejo/forgejo#6843 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7270 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Reviewed-by: 0ko <0ko@noreply.codeberg.org> Co-authored-by: Gusted <postmaster@gusted.xyz> Co-committed-by: Gusted <postmaster@gusted.xyz>
11 lines
205 B
YAML
11 lines
205 B
YAML
-
|
|
id: 1001
|
|
title: Org project that contains private issues
|
|
owner_id: 3
|
|
repo_id: 0
|
|
is_closed: false
|
|
creator_id: 2
|
|
board_type: 1
|
|
type: 3
|
|
created_unix: 1738000000
|
|
updated_unix: 1738000000
|