2017-01-01 13:15:09 -05:00
|
|
|
-
|
|
|
|
|
id: 1
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2017-01-01 13:15:09 -05:00
|
|
|
lower_name: repo1
|
|
|
|
|
name: repo1
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 4
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-08 01:29:21 -05:00
|
|
|
num_issues: 2
|
2017-02-05 22:43:31 -05:00
|
|
|
num_closed_issues: 1
|
2020-01-17 01:03:40 -05:00
|
|
|
num_pulls: 3
|
2017-01-01 13:15:09 -05:00
|
|
|
num_closed_pulls: 0
|
2019-06-05 20:37:45 -04:00
|
|
|
num_milestones: 3
|
|
|
|
|
num_closed_milestones: 1
|
2020-08-16 23:07:38 -04:00
|
|
|
num_projects: 1
|
|
|
|
|
num_closed_projects: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
2023-03-15 17:51:39 -04:00
|
|
|
size: 7320
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-01-01 13:15:09 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 2
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2017-01-01 13:15:09 -05:00
|
|
|
lower_name: repo2
|
|
|
|
|
name: repo2
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 1
|
|
|
|
|
num_forks: 0
|
2019-02-10 14:27:19 -05:00
|
|
|
num_issues: 2
|
2017-01-01 13:15:09 -05:00
|
|
|
num_closed_issues: 1
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: true
|
2017-01-07 22:10:53 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 3
|
|
|
|
|
owner_id: 3
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user3
|
2017-01-07 22:10:53 -05:00
|
|
|
lower_name: repo3
|
|
|
|
|
name: repo3
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-12 02:48:13 -04:00
|
|
|
num_issues: 1
|
2017-01-07 22:10:53 -05:00
|
|
|
num_closed_issues: 0
|
2020-10-20 14:18:25 -04:00
|
|
|
num_pulls: 1
|
2017-01-07 22:10:53 -05:00
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
2020-08-16 23:07:38 -04:00
|
|
|
num_projects: 1
|
|
|
|
|
num_closed_projects: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_private: true
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-01-07 22:10:53 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 4
|
|
|
|
|
owner_id: 5
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user5
|
2017-01-07 22:10:53 -05:00
|
|
|
lower_name: repo4
|
|
|
|
|
name: repo4
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 1
|
|
|
|
|
num_forks: 0
|
2017-01-07 22:10:53 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
2020-08-16 23:07:38 -04:00
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 1
|
2022-10-17 12:23:27 -04:00
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-01-24 11:16:36 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 5
|
|
|
|
|
owner_id: 3
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user3
|
2017-01-24 11:16:36 -05:00
|
|
|
lower_name: repo5
|
|
|
|
|
name: repo5
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2021-08-13 16:47:25 -04:00
|
|
|
num_issues: 1
|
2017-01-24 11:16:36 -05:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-01-24 11:16:36 -05:00
|
|
|
is_mirror: true
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-06 10:18:36 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 6
|
|
|
|
|
owner_id: 10
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user10
|
2017-02-06 10:18:36 -05:00
|
|
|
lower_name: repo6
|
|
|
|
|
name: repo6
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-06 10:18:36 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-02-06 10:18:36 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-06 10:18:36 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 7
|
|
|
|
|
owner_id: 10
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user10
|
2017-02-06 10:18:36 -05:00
|
|
|
lower_name: repo7
|
|
|
|
|
name: repo7
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-06 10:18:36 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-02-06 10:18:36 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-06 10:18:36 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 8
|
|
|
|
|
owner_id: 10
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user10
|
2017-02-06 10:18:36 -05:00
|
|
|
lower_name: repo8
|
|
|
|
|
name: repo8
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-06 10:18:36 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-02-06 10:18:36 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-11 05:57:57 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 9
|
|
|
|
|
owner_id: 11
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user11
|
2017-02-11 05:57:57 -05:00
|
|
|
lower_name: repo9
|
|
|
|
|
name: repo9
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-11 05:57:57 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-02-11 05:57:57 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-15 10:24:23 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 10
|
|
|
|
|
owner_id: 12
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user12
|
2017-02-15 10:24:23 -05:00
|
|
|
lower_name: repo10
|
|
|
|
|
name: repo10
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 1
|
2017-02-15 10:24:23 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
2019-06-30 03:57:59 -04:00
|
|
|
num_pulls: 1
|
2017-02-15 10:24:23 -05:00
|
|
|
num_closed_pulls: 0
|
2021-03-13 13:06:52 -05:00
|
|
|
num_milestones: 1
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2017-02-15 10:24:23 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-15 10:24:23 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 11
|
|
|
|
|
owner_id: 13
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user13
|
2017-02-15 10:24:23 -05:00
|
|
|
lower_name: repo11
|
|
|
|
|
name: repo11
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-15 10:24:23 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2017-02-15 10:24:23 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 10
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-22 08:15:14 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 12
|
|
|
|
|
owner_id: 14
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user14
|
2017-02-22 08:15:14 -05:00
|
|
|
lower_name: test_repo_12
|
|
|
|
|
name: test_repo_12
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-22 08:15:14 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-02-22 08:15:14 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-22 08:15:14 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 13
|
|
|
|
|
owner_id: 14
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user14
|
2017-02-22 08:15:14 -05:00
|
|
|
lower_name: test_repo_13
|
|
|
|
|
name: test_repo_13
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-22 08:15:14 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-02-22 08:15:14 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-02-22 08:15:14 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 14
|
|
|
|
|
owner_id: 14
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user14
|
2017-02-22 08:15:14 -05:00
|
|
|
lower_name: test_repo_14
|
|
|
|
|
name: test_repo_14
|
2019-08-25 13:06:36 -04:00
|
|
|
description: test_description_14
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-02-22 08:15:14 -05:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-02-22 08:15:14 -05:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-07-27 05:23:38 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 15
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2017-07-27 05:23:38 -04:00
|
|
|
lower_name: repo15
|
|
|
|
|
name: repo15
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
2022-02-25 16:22:20 -05:00
|
|
|
is_private: true
|
2022-10-17 12:23:27 -04:00
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-05 09:45:18 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 16
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2017-09-05 09:45:18 -04:00
|
|
|
lower_name: repo16
|
|
|
|
|
name: repo16
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-05 09:45:18 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-22 06:51:16 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 17
|
|
|
|
|
owner_id: 15
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user15
|
2017-09-22 06:51:16 -04:00
|
|
|
lower_name: big_test_public_1
|
|
|
|
|
name: big_test_public_1
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-22 06:51:16 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-09-22 06:51:16 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-22 06:51:16 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 18
|
|
|
|
|
owner_id: 15
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user15
|
2017-09-22 06:51:16 -04:00
|
|
|
lower_name: big_test_public_2
|
|
|
|
|
name: big_test_public_2
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-22 06:51:16 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-09-22 06:51:16 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-22 06:51:16 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 19
|
|
|
|
|
owner_id: 15
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user15
|
2017-09-22 06:51:16 -04:00
|
|
|
lower_name: big_test_private_1
|
|
|
|
|
name: big_test_private_1
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-22 06:51:16 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-09-22 06:51:16 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-22 06:51:16 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 20
|
|
|
|
|
owner_id: 15
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user15
|
2017-09-22 06:51:16 -04:00
|
|
|
lower_name: big_test_private_2
|
|
|
|
|
name: big_test_private_2
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-22 06:51:16 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-09-22 06:51:16 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-22 06:51:16 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 21
|
|
|
|
|
owner_id: 16
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user16
|
2017-09-22 06:51:16 -04:00
|
|
|
lower_name: big_test_public_3
|
|
|
|
|
name: big_test_public_3
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-22 06:51:16 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-09-22 06:51:16 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-22 06:51:16 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 22
|
|
|
|
|
owner_id: 16
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user16
|
2017-09-22 06:51:16 -04:00
|
|
|
lower_name: big_test_private_3
|
|
|
|
|
name: big_test_private_3
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-22 06:51:16 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-09-22 06:51:16 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-22 06:51:16 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 23
|
|
|
|
|
owner_id: 17
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user17
|
2017-09-22 06:51:16 -04:00
|
|
|
lower_name: big_test_public_4
|
|
|
|
|
name: big_test_public_4
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-22 06:51:16 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-09-22 06:51:16 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-09-22 06:51:16 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 24
|
|
|
|
|
owner_id: 17
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user17
|
2017-09-22 06:51:16 -04:00
|
|
|
lower_name: big_test_private_4
|
|
|
|
|
name: big_test_private_4
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-09-22 06:51:16 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-09-22 06:51:16 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-10-26 17:16:13 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 25
|
|
|
|
|
owner_id: 20
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user20
|
2017-10-26 17:16:13 -04:00
|
|
|
lower_name: big_test_public_mirror_5
|
|
|
|
|
name: big_test_public_mirror_5
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-10-26 17:16:13 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-10-26 17:16:13 -04:00
|
|
|
is_mirror: true
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-10-26 17:16:13 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 26
|
|
|
|
|
owner_id: 20
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user20
|
2017-10-26 17:16:13 -04:00
|
|
|
lower_name: big_test_private_mirror_5
|
|
|
|
|
name: big_test_private_mirror_5
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-10-26 17:16:13 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-10-26 17:16:13 -04:00
|
|
|
is_mirror: true
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-10-26 17:16:13 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 27
|
|
|
|
|
owner_id: 19
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user19
|
2017-10-26 17:16:13 -04:00
|
|
|
lower_name: big_test_public_mirror_6
|
|
|
|
|
name: big_test_public_mirror_6
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 1
|
2017-10-26 17:16:13 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-10-26 17:16:13 -04:00
|
|
|
is_mirror: true
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2017-10-26 17:16:13 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 28
|
|
|
|
|
owner_id: 19
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user19
|
2017-10-26 17:16:13 -04:00
|
|
|
lower_name: big_test_private_mirror_6
|
|
|
|
|
name: big_test_private_mirror_6
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 1
|
2017-10-26 17:16:13 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-10-26 17:16:13 -04:00
|
|
|
is_mirror: true
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2018-06-21 12:00:13 -04:00
|
|
|
|
2017-10-26 17:16:13 -04:00
|
|
|
-
|
|
|
|
|
id: 29
|
|
|
|
|
owner_id: 20
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user20
|
2017-10-26 17:16:13 -04:00
|
|
|
lower_name: big_test_public_fork_7
|
|
|
|
|
name: big_test_public_fork_7
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-10-26 17:16:13 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-10-26 17:16:13 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: true
|
|
|
|
|
fork_id: 27
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2018-06-21 12:00:13 -04:00
|
|
|
|
2017-10-26 17:16:13 -04:00
|
|
|
-
|
|
|
|
|
id: 30
|
|
|
|
|
owner_id: 20
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user20
|
2017-10-26 17:16:13 -04:00
|
|
|
lower_name: big_test_private_fork_7
|
|
|
|
|
name: big_test_private_fork_7
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2017-10-26 17:16:13 -04:00
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2017-10-26 17:16:13 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: true
|
|
|
|
|
fork_id: 28
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2018-05-01 03:04:36 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 31
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2018-05-01 03:04:36 -04:00
|
|
|
lower_name: repo20
|
|
|
|
|
name: repo20
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2018-05-01 03:04:36 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2018-05-01 03:04:36 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2018-06-21 12:00:13 -04:00
|
|
|
|
|
|
|
|
-
|
2018-11-28 06:26:14 -05:00
|
|
|
id: 32 # org public repo
|
2018-06-21 12:00:13 -04:00
|
|
|
owner_id: 3
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user3
|
2018-06-21 12:00:13 -04:00
|
|
|
lower_name: repo21
|
|
|
|
|
name: repo21
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2018-06-21 12:00:13 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2022-05-16 05:49:17 -04:00
|
|
|
num_issues: 2
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2018-06-21 12:00:13 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2018-09-06 21:37:02 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 33
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2018-09-06 21:37:02 -04:00
|
|
|
lower_name: utf8
|
|
|
|
|
name: utf8
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
2018-09-06 21:37:02 -04:00
|
|
|
is_private: false
|
2022-10-17 12:23:27 -04:00
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2018-09-12 22:33:48 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 34
|
|
|
|
|
owner_id: 21
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user21
|
2018-09-12 22:33:48 -04:00
|
|
|
lower_name: golang
|
|
|
|
|
name: golang
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2018-09-12 22:33:48 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2018-09-12 22:33:48 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2018-09-12 22:33:48 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 35
|
|
|
|
|
owner_id: 21
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user21
|
2018-09-12 22:33:48 -04:00
|
|
|
lower_name: graphql
|
|
|
|
|
name: graphql
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2018-09-12 22:33:48 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2018-09-12 22:33:48 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-04-11 22:28:44 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 36
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2019-04-11 22:28:44 -04:00
|
|
|
lower_name: commits_search_test
|
|
|
|
|
name: commits_search_test
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-04-11 22:28:44 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-04-11 22:28:44 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-04-17 01:31:08 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 37
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2019-04-17 01:31:08 -04:00
|
|
|
lower_name: git_hooks_test
|
|
|
|
|
name: git_hooks_test
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-04-17 01:31:08 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-04-17 01:31:08 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-04-25 14:59:10 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 38
|
|
|
|
|
owner_id: 22
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: limited_org
|
2019-04-25 14:59:10 -04:00
|
|
|
lower_name: public_repo_on_limited_org
|
|
|
|
|
name: public_repo_on_limited_org
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-04-25 14:59:10 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-04-25 14:59:10 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-04-25 14:59:10 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 39
|
|
|
|
|
owner_id: 22
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: limited_org
|
2019-04-25 14:59:10 -04:00
|
|
|
lower_name: private_repo_on_limited_org
|
|
|
|
|
name: private_repo_on_limited_org
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-04-25 14:59:10 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-04-25 14:59:10 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-04-25 14:59:10 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 40
|
|
|
|
|
owner_id: 23
|
2021-10-27 22:54:40 -04:00
|
|
|
owner_name: privated_org
|
2019-04-25 14:59:10 -04:00
|
|
|
lower_name: public_repo_on_private_org
|
|
|
|
|
name: public_repo_on_private_org
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-04-25 14:59:10 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-04-25 14:59:10 -04:00
|
|
|
is_mirror: false
|
2019-10-13 09:23:14 -04:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-04-25 14:59:10 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 41
|
|
|
|
|
owner_id: 23
|
2021-10-27 22:54:40 -04:00
|
|
|
owner_name: privated_org
|
2019-04-25 14:59:10 -04:00
|
|
|
lower_name: private_repo_on_private_org
|
|
|
|
|
name: private_repo_on_private_org
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-04-25 14:59:10 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-09-11 13:26:28 -04:00
|
|
|
is_mirror: false
|
2022-10-17 12:23:27 -04:00
|
|
|
status: 0
|
|
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-09-11 13:26:28 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 42
|
|
|
|
|
owner_id: 2
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user2
|
2019-09-11 13:26:28 -04:00
|
|
|
lower_name: glob
|
|
|
|
|
name: glob
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-09-11 13:26:28 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2020-01-01 17:51:10 -05:00
|
|
|
num_issues: 1
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
2020-01-01 17:51:10 -05:00
|
|
|
num_milestones: 1
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
2022-06-04 14:30:01 -04:00
|
|
|
is_archived: false
|
2022-10-17 12:23:27 -04:00
|
|
|
is_mirror: false
|
|
|
|
|
status: 0
|
|
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-09-23 16:08:03 -04:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 43
|
|
|
|
|
owner_id: 26
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: org26
|
2019-09-23 16:08:03 -04:00
|
|
|
lower_name: repo26
|
|
|
|
|
name: repo26
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-09-23 16:08:03 -04:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: true
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2019-10-13 09:23:14 -04:00
|
|
|
is_mirror: false
|
|
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-11-11 10:15:29 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 44
|
|
|
|
|
owner_id: 27
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user27
|
2019-11-11 10:15:29 -05:00
|
|
|
lower_name: template1
|
|
|
|
|
name: template1
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-11-11 10:15:29 -05:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-11-11 10:15:29 -05:00
|
|
|
is_mirror: false
|
|
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: true
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-11-11 10:15:29 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 45
|
|
|
|
|
owner_id: 27
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: user27
|
2019-11-11 10:15:29 -05:00
|
|
|
lower_name: template2
|
|
|
|
|
name: template2
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-11-11 10:15:29 -05:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
2019-11-11 10:15:29 -05:00
|
|
|
is_mirror: false
|
|
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: true
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-12-06 23:21:18 -05:00
|
|
|
|
2020-01-01 17:51:10 -05:00
|
|
|
-
|
2019-12-06 23:21:18 -05:00
|
|
|
id: 46
|
|
|
|
|
owner_id: 26
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: org26
|
2019-12-06 23:21:18 -05:00
|
|
|
lower_name: repo_external_tracker
|
|
|
|
|
name: repo_external_tracker
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-12-06 23:21:18 -05:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-12-06 23:21:18 -05:00
|
|
|
is_mirror: false
|
|
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-12-06 23:21:18 -05:00
|
|
|
|
2020-01-01 17:51:10 -05:00
|
|
|
-
|
2019-12-06 23:21:18 -05:00
|
|
|
id: 47
|
|
|
|
|
owner_id: 26
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: org26
|
2019-12-06 23:21:18 -05:00
|
|
|
lower_name: repo_external_tracker_numeric
|
|
|
|
|
name: repo_external_tracker_numeric
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-12-06 23:21:18 -05:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-12-06 23:21:18 -05:00
|
|
|
is_mirror: false
|
|
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2019-12-06 23:21:18 -05:00
|
|
|
|
2020-01-01 17:51:10 -05:00
|
|
|
-
|
2019-12-06 23:21:18 -05:00
|
|
|
id: 48
|
|
|
|
|
owner_id: 26
|
2020-01-12 04:36:21 -05:00
|
|
|
owner_name: org26
|
2019-12-06 23:21:18 -05:00
|
|
|
lower_name: repo_external_tracker_alpha
|
|
|
|
|
name: repo_external_tracker_alpha
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
2019-12-06 23:21:18 -05:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
2019-12-06 23:21:18 -05:00
|
|
|
num_pulls: 1
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
2019-12-06 23:21:18 -05:00
|
|
|
is_mirror: false
|
|
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
[RFC] Make archival asynchronous (#11296)
* Make archival asynchronous
The prime benefit being sought here is for large archives to not
clog up the rendering process and cause unsightly proxy timeouts.
As a secondary benefit, archive-in-progress is moved out of the
way into a /tmp file so that new archival requests for the same
commit will not get fulfilled based on an archive that isn't yet
finished.
This asynchronous system is fairly primitive; request comes in, we'll
spawn off a new goroutine to handle it, then we'll mark it as done.
Status requests will see if the file exists in the final location,
and report the archival as done when it exists.
Fixes #11265
* Archive links: drop initial delay to three-quarters of a second
Some, or perhaps even most, archives will not take all that long to archive.
The archive process starts as soon as the download button is initially
clicked, so in theory they could be done quite quickly. Drop the initial
delay down to three-quarters of a second to make it more responsive in the
common case of the archive being quickly created.
* archiver: restructure a little bit to facilitate testing
This introduces two sync.Cond pointers to the archiver package. If they're
non-nil when we go to process a request, we'll wait until signalled (at all)
to proceed. The tests will then create the sync.Cond so that it can signal
at-will and sanity-check the state of the queue at different phases.
The author believes that nil-checking these two sync.Cond pointers on every
archive processing will introduce minimal overhead with no impact on
maintainability.
* gofmt nit: no space around binary + operator
* services: archiver: appease golangci-lint, lock queueMutex
Locking/unlocking the queueMutex is allowed, but not required, for
Cond.Signal() and Cond.Broadcast(). The magic at play here is just a little
too much for golangci-lint, as we take the address of queueMutex and this is
mostly used in archiver.go; the variable still gets flagged as unused.
* archiver: tests: fix several timing nits
Once we've signaled a cond var, it may take some small amount of time for
the goroutines released to hit the spot we're wanting them to be at. Give
them an appropriate amount of time.
* archiver: tests: no underscore in var name, ungh
* archiver: tests: Test* is run in a separate context than TestMain
We must setup the mutex/cond variables at the beginning of any test that's
going to use it, or else these will be nil when the test is actually ran.
* archiver: tests: hopefully final tweak
Things got shuffled around such that we carefully build up and release
requests from the queue, so we can validate the state of the queue at each
step. Fix some assertions that no longer hold true as fallout.
* repo: Download: restore some semblance of previous behavior
When archival was made async, the GET endpoint was only useful if a previous
POST had initiated the download. This commit restores the previous behavior,
to an extent; we'll now submit the archive request there and return a
"202 Accepted" to indicate that it's processing if we didn't manage to
complete the request within ~2 seconds of submission.
This lets a client directly GET the archive, and gives them some indication
that they may attempt to GET it again at a later time.
* archiver: tests: simplify a bit further
We don't need to risk failure and use time.ParseDuration to get 2 *
time.Second.
else if isn't really necessary if the conditions are simple enough and lead
to the same result.
* archiver: tests: resolve potential source of flakiness
Increase all timeouts to 10 seconds; these aren't hard-coded sleeps, so
there's no guarantee we'll actually take that long. If we need longer to
not have a false-positive, then so be it.
While here, various assert.{Not,}Equal arguments are flipped around so that
the wording in error output reflects reality, where the expected argument is
second and actual third.
* archiver: setup infrastructure for notifying consumers of completion
This API will *not* allow consumers to subscribe to specific requests being
completed, just *any* request being completed. The caller is responsible for
determining if their request is satisfied and waiting again if needed.
* repo: archive: make GET endpoint synchronous again
If the request isn't complete, this endpoint will now submit the request and
wait for completion using the new API. This may still be susceptible to
timeouts for larger repos, but other endpoints now exist that the web
interface will use to negotiate its way through larger archive processes.
* archiver: tests: amend test to include WaitForCompletion()
This is a trivial one, so go ahead and include it.
* archiver: tests: fix test by calling NewContext()
The mutex is otherwise uninitialized, so we need to ensure that we're
actually initializing it if we plan to test it.
* archiver: tests: integrate new WaitForCompletion a little better
We can use this to wait for archives to come in, rather than spinning and
hoping with a timeout.
* archiver: tests: combine numQueued declaration with next-instruction assignment
* routers: repo: reap unused archiving flag from DownloadStatus()
This had some planned usage before, indicating whether this request
initiated the archival process or not. After several rounds of refactoring,
this use was deemed not necessary for much of anything and got boiled down
to !complete in all cases.
* services: archiver: restructure to use a channel
We now offer two forms of waiting for a request:
- WaitForCompletion: wait for completion with no timeout
- TimedWaitForCompletion: wait for completion with timeout
In both cases, we wait for the given request's cchan to close; in the latter
case, we do so with the caller-provided timeout. This completely removes the
need for busy-wait loops in Download/InitiateDownload, as it's fairly clean
to wait on a channel with timeout.
* services: archiver: use defer to unlock now that we can
This previously carried the lock into the goroutine, but an intermediate
step just added the request to archiveInProgress outside of the new
goroutine and removed the need for the goroutine to start out with it.
* Revert "archiver: tests: combine numQueued declaration with next-instruction assignment"
This reverts commit bcc52140238e16680f2e05e448e9be51372afdf5.
Revert "archiver: tests: integrate new WaitForCompletion a little better"
This reverts commit 9fc8bedb5667d24d3a3c7843dc28a229efffb1e6.
Revert "archiver: tests: fix test by calling NewContext()"
This reverts commit 709c35685eaaf261ebbb7d3420e3376a4ee8e7f2.
Revert "archiver: tests: amend test to include WaitForCompletion()"
This reverts commit 75261f56bc05d1fa8ff7e81dcbc0ccd93fdc9d50.
* archiver: tests: first attempt at WaitForCompletion() tests
* archiver: tests: slight improvement, less busy-loop
Just wait for the requests to complete in order, instead of busy-waiting
with a timeout. This is slightly less fragile.
While here, reverse the arguments of a nearby assert.Equal() so that
expected/actual are correct in any test output.
* archiver: address lint nits
* services: archiver: only close the channel once
* services: archiver: use a struct{} for the wait channel
This makes it obvious that the channel is only being used as a signal,
rather than anything useful being piped through it.
* archiver: tests: fix expectations
Move the close of the channel into doArchive() itself; notably, before these
goroutines move on to waiting on the Release cond.
The tests are adjusted to reflect that we can't WaitForCompletion() after
they've already completed, as WaitForCompletion() doesn't indicate that
they've been released from the queue yet.
* archiver: tests: set cchan to nil for comparison
* archiver: move ctx.Error's back into the route handlers
We shouldn't be setting this in a service, we should just be validating the
request that we were handed.
* services: archiver: use regex to match a hash
This makes sure we don't try and use refName as a hash when it's clearly not
one, e.g. heads/pull/foo.
* routers: repo: remove the weird /archive/status endpoint
We don't need to do this anymore, we can just continue POSTing to the
archive/* endpoint until we're told the download's complete. This avoids a
potential naming conflict, where a ref could start with "status/"
* archiver: tests: bump reasonable timeout to 15s
* archiver: tests: actually release timedReq
* archiver: tests: run through inFlight instead of manually checking
While we're here, add a test for manually re-processing an archive that's
already been complete. Re-open the channel and mark it incomplete, so that
doArchive can just mark it complete again.
* initArchiveLinks: prevent default behavior from clicking
* archiver: alias gitea's context, golang context import pending
* archiver: simplify logic, just reconstruct slices
While the previous logic was perhaps slightly more efficient, the
new variant's readability is much improved.
* archiver: don't block shutdown on waiting for archive
The technique established launches a goroutine to do the wait,
which will close a wait channel upon termination. For the timeout
case, we also send back a value indicating whether the timeout was
hit or not.
The timeouts are expected to be relatively small, but still a multi-
second delay to shutdown due to this could be unfortunate.
* archiver: simplify shutdown logic
We can just grab the shutdown channel from the graceful manager instead of
constructing a channel to halt the caller and/or pass a result back.
* Style issues
* Fix mis-merge
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Lauris BH <lauris@nix.lv>
2020-11-07 15:27:28 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 49
|
|
|
|
|
owner_id: 27
|
|
|
|
|
owner_name: user27
|
|
|
|
|
lower_name: repo49
|
|
|
|
|
name: repo49
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
[RFC] Make archival asynchronous (#11296)
* Make archival asynchronous
The prime benefit being sought here is for large archives to not
clog up the rendering process and cause unsightly proxy timeouts.
As a secondary benefit, archive-in-progress is moved out of the
way into a /tmp file so that new archival requests for the same
commit will not get fulfilled based on an archive that isn't yet
finished.
This asynchronous system is fairly primitive; request comes in, we'll
spawn off a new goroutine to handle it, then we'll mark it as done.
Status requests will see if the file exists in the final location,
and report the archival as done when it exists.
Fixes #11265
* Archive links: drop initial delay to three-quarters of a second
Some, or perhaps even most, archives will not take all that long to archive.
The archive process starts as soon as the download button is initially
clicked, so in theory they could be done quite quickly. Drop the initial
delay down to three-quarters of a second to make it more responsive in the
common case of the archive being quickly created.
* archiver: restructure a little bit to facilitate testing
This introduces two sync.Cond pointers to the archiver package. If they're
non-nil when we go to process a request, we'll wait until signalled (at all)
to proceed. The tests will then create the sync.Cond so that it can signal
at-will and sanity-check the state of the queue at different phases.
The author believes that nil-checking these two sync.Cond pointers on every
archive processing will introduce minimal overhead with no impact on
maintainability.
* gofmt nit: no space around binary + operator
* services: archiver: appease golangci-lint, lock queueMutex
Locking/unlocking the queueMutex is allowed, but not required, for
Cond.Signal() and Cond.Broadcast(). The magic at play here is just a little
too much for golangci-lint, as we take the address of queueMutex and this is
mostly used in archiver.go; the variable still gets flagged as unused.
* archiver: tests: fix several timing nits
Once we've signaled a cond var, it may take some small amount of time for
the goroutines released to hit the spot we're wanting them to be at. Give
them an appropriate amount of time.
* archiver: tests: no underscore in var name, ungh
* archiver: tests: Test* is run in a separate context than TestMain
We must setup the mutex/cond variables at the beginning of any test that's
going to use it, or else these will be nil when the test is actually ran.
* archiver: tests: hopefully final tweak
Things got shuffled around such that we carefully build up and release
requests from the queue, so we can validate the state of the queue at each
step. Fix some assertions that no longer hold true as fallout.
* repo: Download: restore some semblance of previous behavior
When archival was made async, the GET endpoint was only useful if a previous
POST had initiated the download. This commit restores the previous behavior,
to an extent; we'll now submit the archive request there and return a
"202 Accepted" to indicate that it's processing if we didn't manage to
complete the request within ~2 seconds of submission.
This lets a client directly GET the archive, and gives them some indication
that they may attempt to GET it again at a later time.
* archiver: tests: simplify a bit further
We don't need to risk failure and use time.ParseDuration to get 2 *
time.Second.
else if isn't really necessary if the conditions are simple enough and lead
to the same result.
* archiver: tests: resolve potential source of flakiness
Increase all timeouts to 10 seconds; these aren't hard-coded sleeps, so
there's no guarantee we'll actually take that long. If we need longer to
not have a false-positive, then so be it.
While here, various assert.{Not,}Equal arguments are flipped around so that
the wording in error output reflects reality, where the expected argument is
second and actual third.
* archiver: setup infrastructure for notifying consumers of completion
This API will *not* allow consumers to subscribe to specific requests being
completed, just *any* request being completed. The caller is responsible for
determining if their request is satisfied and waiting again if needed.
* repo: archive: make GET endpoint synchronous again
If the request isn't complete, this endpoint will now submit the request and
wait for completion using the new API. This may still be susceptible to
timeouts for larger repos, but other endpoints now exist that the web
interface will use to negotiate its way through larger archive processes.
* archiver: tests: amend test to include WaitForCompletion()
This is a trivial one, so go ahead and include it.
* archiver: tests: fix test by calling NewContext()
The mutex is otherwise uninitialized, so we need to ensure that we're
actually initializing it if we plan to test it.
* archiver: tests: integrate new WaitForCompletion a little better
We can use this to wait for archives to come in, rather than spinning and
hoping with a timeout.
* archiver: tests: combine numQueued declaration with next-instruction assignment
* routers: repo: reap unused archiving flag from DownloadStatus()
This had some planned usage before, indicating whether this request
initiated the archival process or not. After several rounds of refactoring,
this use was deemed not necessary for much of anything and got boiled down
to !complete in all cases.
* services: archiver: restructure to use a channel
We now offer two forms of waiting for a request:
- WaitForCompletion: wait for completion with no timeout
- TimedWaitForCompletion: wait for completion with timeout
In both cases, we wait for the given request's cchan to close; in the latter
case, we do so with the caller-provided timeout. This completely removes the
need for busy-wait loops in Download/InitiateDownload, as it's fairly clean
to wait on a channel with timeout.
* services: archiver: use defer to unlock now that we can
This previously carried the lock into the goroutine, but an intermediate
step just added the request to archiveInProgress outside of the new
goroutine and removed the need for the goroutine to start out with it.
* Revert "archiver: tests: combine numQueued declaration with next-instruction assignment"
This reverts commit bcc52140238e16680f2e05e448e9be51372afdf5.
Revert "archiver: tests: integrate new WaitForCompletion a little better"
This reverts commit 9fc8bedb5667d24d3a3c7843dc28a229efffb1e6.
Revert "archiver: tests: fix test by calling NewContext()"
This reverts commit 709c35685eaaf261ebbb7d3420e3376a4ee8e7f2.
Revert "archiver: tests: amend test to include WaitForCompletion()"
This reverts commit 75261f56bc05d1fa8ff7e81dcbc0ccd93fdc9d50.
* archiver: tests: first attempt at WaitForCompletion() tests
* archiver: tests: slight improvement, less busy-loop
Just wait for the requests to complete in order, instead of busy-waiting
with a timeout. This is slightly less fragile.
While here, reverse the arguments of a nearby assert.Equal() so that
expected/actual are correct in any test output.
* archiver: address lint nits
* services: archiver: only close the channel once
* services: archiver: use a struct{} for the wait channel
This makes it obvious that the channel is only being used as a signal,
rather than anything useful being piped through it.
* archiver: tests: fix expectations
Move the close of the channel into doArchive() itself; notably, before these
goroutines move on to waiting on the Release cond.
The tests are adjusted to reflect that we can't WaitForCompletion() after
they've already completed, as WaitForCompletion() doesn't indicate that
they've been released from the queue yet.
* archiver: tests: set cchan to nil for comparison
* archiver: move ctx.Error's back into the route handlers
We shouldn't be setting this in a service, we should just be validating the
request that we were handed.
* services: archiver: use regex to match a hash
This makes sure we don't try and use refName as a hash when it's clearly not
one, e.g. heads/pull/foo.
* routers: repo: remove the weird /archive/status endpoint
We don't need to do this anymore, we can just continue POSTing to the
archive/* endpoint until we're told the download's complete. This avoids a
potential naming conflict, where a ref could start with "status/"
* archiver: tests: bump reasonable timeout to 15s
* archiver: tests: actually release timedReq
* archiver: tests: run through inFlight instead of manually checking
While we're here, add a test for manually re-processing an archive that's
already been complete. Re-open the channel and mark it incomplete, so that
doArchive can just mark it complete again.
* initArchiveLinks: prevent default behavior from clicking
* archiver: alias gitea's context, golang context import pending
* archiver: simplify logic, just reconstruct slices
While the previous logic was perhaps slightly more efficient, the
new variant's readability is much improved.
* archiver: don't block shutdown on waiting for archive
The technique established launches a goroutine to do the wait,
which will close a wait channel upon termination. For the timeout
case, we also send back a value indicating whether the timeout was
hit or not.
The timeouts are expected to be relatively small, but still a multi-
second delay to shutdown due to this could be unfortunate.
* archiver: simplify shutdown logic
We can just grab the shutdown channel from the graceful manager instead of
constructing a channel to halt the caller and/or pass a result back.
* Style issues
* Fix mis-merge
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Lauris BH <lauris@nix.lv>
2020-11-07 15:27:28 -05:00
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
[RFC] Make archival asynchronous (#11296)
* Make archival asynchronous
The prime benefit being sought here is for large archives to not
clog up the rendering process and cause unsightly proxy timeouts.
As a secondary benefit, archive-in-progress is moved out of the
way into a /tmp file so that new archival requests for the same
commit will not get fulfilled based on an archive that isn't yet
finished.
This asynchronous system is fairly primitive; request comes in, we'll
spawn off a new goroutine to handle it, then we'll mark it as done.
Status requests will see if the file exists in the final location,
and report the archival as done when it exists.
Fixes #11265
* Archive links: drop initial delay to three-quarters of a second
Some, or perhaps even most, archives will not take all that long to archive.
The archive process starts as soon as the download button is initially
clicked, so in theory they could be done quite quickly. Drop the initial
delay down to three-quarters of a second to make it more responsive in the
common case of the archive being quickly created.
* archiver: restructure a little bit to facilitate testing
This introduces two sync.Cond pointers to the archiver package. If they're
non-nil when we go to process a request, we'll wait until signalled (at all)
to proceed. The tests will then create the sync.Cond so that it can signal
at-will and sanity-check the state of the queue at different phases.
The author believes that nil-checking these two sync.Cond pointers on every
archive processing will introduce minimal overhead with no impact on
maintainability.
* gofmt nit: no space around binary + operator
* services: archiver: appease golangci-lint, lock queueMutex
Locking/unlocking the queueMutex is allowed, but not required, for
Cond.Signal() and Cond.Broadcast(). The magic at play here is just a little
too much for golangci-lint, as we take the address of queueMutex and this is
mostly used in archiver.go; the variable still gets flagged as unused.
* archiver: tests: fix several timing nits
Once we've signaled a cond var, it may take some small amount of time for
the goroutines released to hit the spot we're wanting them to be at. Give
them an appropriate amount of time.
* archiver: tests: no underscore in var name, ungh
* archiver: tests: Test* is run in a separate context than TestMain
We must setup the mutex/cond variables at the beginning of any test that's
going to use it, or else these will be nil when the test is actually ran.
* archiver: tests: hopefully final tweak
Things got shuffled around such that we carefully build up and release
requests from the queue, so we can validate the state of the queue at each
step. Fix some assertions that no longer hold true as fallout.
* repo: Download: restore some semblance of previous behavior
When archival was made async, the GET endpoint was only useful if a previous
POST had initiated the download. This commit restores the previous behavior,
to an extent; we'll now submit the archive request there and return a
"202 Accepted" to indicate that it's processing if we didn't manage to
complete the request within ~2 seconds of submission.
This lets a client directly GET the archive, and gives them some indication
that they may attempt to GET it again at a later time.
* archiver: tests: simplify a bit further
We don't need to risk failure and use time.ParseDuration to get 2 *
time.Second.
else if isn't really necessary if the conditions are simple enough and lead
to the same result.
* archiver: tests: resolve potential source of flakiness
Increase all timeouts to 10 seconds; these aren't hard-coded sleeps, so
there's no guarantee we'll actually take that long. If we need longer to
not have a false-positive, then so be it.
While here, various assert.{Not,}Equal arguments are flipped around so that
the wording in error output reflects reality, where the expected argument is
second and actual third.
* archiver: setup infrastructure for notifying consumers of completion
This API will *not* allow consumers to subscribe to specific requests being
completed, just *any* request being completed. The caller is responsible for
determining if their request is satisfied and waiting again if needed.
* repo: archive: make GET endpoint synchronous again
If the request isn't complete, this endpoint will now submit the request and
wait for completion using the new API. This may still be susceptible to
timeouts for larger repos, but other endpoints now exist that the web
interface will use to negotiate its way through larger archive processes.
* archiver: tests: amend test to include WaitForCompletion()
This is a trivial one, so go ahead and include it.
* archiver: tests: fix test by calling NewContext()
The mutex is otherwise uninitialized, so we need to ensure that we're
actually initializing it if we plan to test it.
* archiver: tests: integrate new WaitForCompletion a little better
We can use this to wait for archives to come in, rather than spinning and
hoping with a timeout.
* archiver: tests: combine numQueued declaration with next-instruction assignment
* routers: repo: reap unused archiving flag from DownloadStatus()
This had some planned usage before, indicating whether this request
initiated the archival process or not. After several rounds of refactoring,
this use was deemed not necessary for much of anything and got boiled down
to !complete in all cases.
* services: archiver: restructure to use a channel
We now offer two forms of waiting for a request:
- WaitForCompletion: wait for completion with no timeout
- TimedWaitForCompletion: wait for completion with timeout
In both cases, we wait for the given request's cchan to close; in the latter
case, we do so with the caller-provided timeout. This completely removes the
need for busy-wait loops in Download/InitiateDownload, as it's fairly clean
to wait on a channel with timeout.
* services: archiver: use defer to unlock now that we can
This previously carried the lock into the goroutine, but an intermediate
step just added the request to archiveInProgress outside of the new
goroutine and removed the need for the goroutine to start out with it.
* Revert "archiver: tests: combine numQueued declaration with next-instruction assignment"
This reverts commit bcc52140238e16680f2e05e448e9be51372afdf5.
Revert "archiver: tests: integrate new WaitForCompletion a little better"
This reverts commit 9fc8bedb5667d24d3a3c7843dc28a229efffb1e6.
Revert "archiver: tests: fix test by calling NewContext()"
This reverts commit 709c35685eaaf261ebbb7d3420e3376a4ee8e7f2.
Revert "archiver: tests: amend test to include WaitForCompletion()"
This reverts commit 75261f56bc05d1fa8ff7e81dcbc0ccd93fdc9d50.
* archiver: tests: first attempt at WaitForCompletion() tests
* archiver: tests: slight improvement, less busy-loop
Just wait for the requests to complete in order, instead of busy-waiting
with a timeout. This is slightly less fragile.
While here, reverse the arguments of a nearby assert.Equal() so that
expected/actual are correct in any test output.
* archiver: address lint nits
* services: archiver: only close the channel once
* services: archiver: use a struct{} for the wait channel
This makes it obvious that the channel is only being used as a signal,
rather than anything useful being piped through it.
* archiver: tests: fix expectations
Move the close of the channel into doArchive() itself; notably, before these
goroutines move on to waiting on the Release cond.
The tests are adjusted to reflect that we can't WaitForCompletion() after
they've already completed, as WaitForCompletion() doesn't indicate that
they've been released from the queue yet.
* archiver: tests: set cchan to nil for comparison
* archiver: move ctx.Error's back into the route handlers
We shouldn't be setting this in a service, we should just be validating the
request that we were handed.
* services: archiver: use regex to match a hash
This makes sure we don't try and use refName as a hash when it's clearly not
one, e.g. heads/pull/foo.
* routers: repo: remove the weird /archive/status endpoint
We don't need to do this anymore, we can just continue POSTing to the
archive/* endpoint until we're told the download's complete. This avoids a
potential naming conflict, where a ref could start with "status/"
* archiver: tests: bump reasonable timeout to 15s
* archiver: tests: actually release timedReq
* archiver: tests: run through inFlight instead of manually checking
While we're here, add a test for manually re-processing an archive that's
already been complete. Re-open the channel and mark it incomplete, so that
doArchive can just mark it complete again.
* initArchiveLinks: prevent default behavior from clicking
* archiver: alias gitea's context, golang context import pending
* archiver: simplify logic, just reconstruct slices
While the previous logic was perhaps slightly more efficient, the
new variant's readability is much improved.
* archiver: don't block shutdown on waiting for archive
The technique established launches a goroutine to do the wait,
which will close a wait channel upon termination. For the timeout
case, we also send back a value indicating whether the timeout was
hit or not.
The timeouts are expected to be relatively small, but still a multi-
second delay to shutdown due to this could be unfortunate.
* archiver: simplify shutdown logic
We can just grab the shutdown channel from the graceful manager instead of
constructing a channel to halt the caller and/or pass a result back.
* Style issues
* Fix mis-merge
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Lauris BH <lauris@nix.lv>
2020-11-07 15:27:28 -05:00
|
|
|
is_mirror: false
|
|
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2021-01-12 23:19:17 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 50
|
|
|
|
|
owner_id: 30
|
|
|
|
|
owner_name: user30
|
|
|
|
|
lower_name: repo50
|
|
|
|
|
name: repo50
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2021-01-12 23:19:17 -05:00
|
|
|
num_issues: 1
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2021-01-12 23:19:17 -05:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2021-01-12 23:19:17 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 51
|
|
|
|
|
owner_id: 30
|
|
|
|
|
owner_name: user30
|
|
|
|
|
lower_name: repo51
|
|
|
|
|
name: repo51
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
2021-01-12 23:19:17 -05:00
|
|
|
num_issues: 1
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_private: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: true
|
|
|
|
|
is_mirror: false
|
2021-03-13 13:06:52 -05:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2022-02-26 01:15:25 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 52
|
|
|
|
|
owner_id: 30
|
|
|
|
|
owner_name: user30
|
|
|
|
|
lower_name: empty
|
|
|
|
|
name: empty
|
2022-10-17 12:23:27 -04:00
|
|
|
num_watches: 0
|
|
|
|
|
num_stars: 0
|
|
|
|
|
num_forks: 0
|
|
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
2022-02-26 01:15:25 -05:00
|
|
|
is_private: true
|
2022-10-17 12:23:27 -04:00
|
|
|
is_empty: true
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_mirror: false
|
2022-02-26 01:15:25 -05:00
|
|
|
status: 0
|
2022-10-17 12:23:27 -04:00
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2022-12-12 07:45:21 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 53
|
|
|
|
|
owner_id: 30
|
|
|
|
|
owner_name: user30
|
|
|
|
|
lower_name: renderer
|
|
|
|
|
name: renderer
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-12-12 07:45:21 -05:00
|
|
|
is_archived: false
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_private: false
|
|
|
|
|
num_issues: 0
|
|
|
|
|
num_closed_issues: 0
|
|
|
|
|
num_pulls: 0
|
|
|
|
|
num_closed_pulls: 0
|
|
|
|
|
num_milestones: 0
|
|
|
|
|
num_closed_milestones: 0
|
|
|
|
|
num_watches: 0
|
|
|
|
|
num_projects: 0
|
|
|
|
|
num_closed_projects: 0
|
|
|
|
|
status: 0
|
|
|
|
|
is_fork: false
|
|
|
|
|
fork_id: 0
|
|
|
|
|
is_template: false
|
|
|
|
|
template_id: 0
|
|
|
|
|
size: 0
|
|
|
|
|
is_fsck_enabled: true
|
|
|
|
|
close_issues_via_commit_in_any_branch: false
|
2022-12-22 18:41:56 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 54
|
|
|
|
|
owner_id: 2
|
|
|
|
|
owner_name: user2
|
|
|
|
|
lower_name: lfs
|
|
|
|
|
name: lfs
|
Do not overwrite empty DefaultBranch (#22708)
Fix #21994.
And fix #19470.
While generating new repo from a template, it does something like
"commit to git repo, re-fetch repo model from DB, and update default
branch if it's empty".
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/modules/repository/generate.go#L241-L253
Unfortunately, when load repo from DB, the default branch will be set to
`setting.Repository.DefaultBranch` if it's empty:
https://github.com/go-gitea/gitea/blob/19d5b2f922c2defde579a935fbedb680eb8fff18/models/repo/repo.go#L228-L233
I believe it's a very old temporary patch but has been kept for many
years, see:
[2d2d85bb](https://github.com/go-gitea/gitea/commit/2d2d85bb#diff-1851799b06733db4df3ec74385c1e8850ee5aedee70b8b55366910d22725eea8)
I know it's a risk to delete it, may lead to potential behavioral
changes, but we cannot keep the outdated `FIXME` forever. On the other
hand, an empty `DefaultBranch` does make sense: an empty repo doesn't
have one conceptually (actually, Gitea will still set it to
`setting.Repository.DefaultBranch` to make it safer).
2023-02-02 15:48:48 -05:00
|
|
|
default_branch: master
|
2022-12-22 18:41:56 -05:00
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_private: true
|
|
|
|
|
status: 0
|
Scoped labels (#22585)
Add a new "exclusive" option per label. This makes it so that when the
label is named `scope/name`, no other label with the same `scope/`
prefix can be set on an issue.
The scope is determined by the last occurence of `/`, so for example
`scope/alpha/name` and `scope/beta/name` are considered to be in
different scopes and can coexist.
Exclusive scopes are not enforced by any database rules, however they
are enforced when editing labels at the models level, automatically
removing any existing labels in the same scope when either attaching a
new label or replacing all labels.
In menus use a circle instead of checkbox to indicate they function as
radio buttons per scope. Issue filtering by label ensures that only a
single scoped label is selected at a time. Clicking with alt key can be
used to remove a scoped label, both when editing individual issues and
batch editing.
Label rendering refactor for consistency and code simplification:
* Labels now consistently have the same shape, emojis and tooltips
everywhere. This includes the label list and label assignment menus.
* In label list, show description below label same as label menus.
* Don't use exactly black/white text colors to look a bit nicer.
* Simplify text color computation. There is no point computing luminance
in linear color space, as this is a perceptual problem and sRGB is
closer to perceptually linear.
* Increase height of label assignment menus to show more labels. Showing
only 3-4 labels at a time leads to a lot of scrolling.
* Render all labels with a new RenderLabel template helper function.
Label creation and editing in multiline modal menu:
* Change label creation to open a modal menu like label editing.
* Change menu layout to place name, description and colors on separate
lines.
* Don't color cancel button red in label editing modal menu.
* Align text to the left in model menu for better readability and
consistent with settings layout elsewhere.
Custom exclusive scoped label rendering:
* Display scoped label prefix and suffix with slightly darker and
lighter background color respectively, and a slanted edge between them
similar to the `/` symbol.
* In menus exclusive labels are grouped with a divider line.
---------
Co-authored-by: Yarden Shoham <hrsi88@gmail.com>
Co-authored-by: Lauris BH <lauris@nix.lv>
2023-02-18 14:17:39 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 55
|
|
|
|
|
owner_id: 2
|
|
|
|
|
owner_name: user2
|
|
|
|
|
lower_name: scoped_label
|
|
|
|
|
name: scoped_label
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_private: true
|
|
|
|
|
num_issues: 1
|
|
|
|
|
status: 0
|
2023-03-08 20:24:23 -05:00
|
|
|
|
|
|
|
|
-
|
|
|
|
|
id: 56
|
|
|
|
|
owner_id: 2
|
|
|
|
|
owner_name: user2
|
|
|
|
|
lower_name: readme-test
|
|
|
|
|
name: readme-test
|
|
|
|
|
default_branch: master
|
|
|
|
|
is_empty: false
|
|
|
|
|
is_archived: false
|
|
|
|
|
is_private: true
|
|
|
|
|
status: 0
|
|
|
|
|
num_issues: 0
|