forgejo/models/fixtures/issue_index.yml

-
  group_id: 1
  max_index: 5
-
  group_id: 2
  max_index: 2
-
  group_id: 3
  max_index: 2
-
  group_id: 10
  max_index: 1
-
  group_id: 32
  max_index: 2
-
  group_id: 48
  max_index: 1
-
  group_id: 42
  max_index: 1
-
  group_id: 50
  max_index: 1
-
  group_id: 51
  max_index: 1
Add a new table issue_index to store the max issue index so that issue could be deleted with no duplicated index (#15599) * Add a new table issue_index to store the max issue index so that issue could be deleted with no duplicated index * Fix pull index * Add tests for concurrent creating issues * Fix lint * Fix tests * Fix postgres test * Add test for migration v180 * Rename wrong test file name Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lauris BH <lauris@nix.lv> 2021-06-14 04:22:55 +02:00			`-`
			`group_id: 1`
			`max_index: 5`
			`-`
			`group_id: 2`
			`max_index: 2`
			`-`
			`group_id: 3`
			`max_index: 2`
			`-`
			`group_id: 10`
			`max_index: 1`
Fix issue overview for teams (#19652) - Don't use hacky solution to limit to the correct RepoID's, instead use current code to handle these limits. The existing code is more correct than the hacky solution. - Resolves #19636 - Add test-case 2022-05-16 11:49:17 +02:00			`-`
			`group_id: 32`
			`max_index: 2`
Add a new table issue_index to store the max issue index so that issue could be deleted with no duplicated index (#15599) * Add a new table issue_index to store the max issue index so that issue could be deleted with no duplicated index * Fix pull index * Add tests for concurrent creating issues * Fix lint * Fix tests * Fix postgres test * Add test for migration v180 * Rename wrong test file name Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lauris BH <lauris@nix.lv> 2021-06-14 04:22:55 +02:00			`-`
			`group_id: 48`
			`max_index: 1`
			`-`
			`group_id: 42`
			`max_index: 1`
			`-`
			`group_id: 50`
			`max_index: 1`
			`-`
			`group_id: 51`
Fix issue overview for teams (#19652) - Don't use hacky solution to limit to the correct RepoID's, instead use current code to handle these limits. The existing code is more correct than the hacky solution. - Resolves #19636 - Add test-case 2022-05-16 11:49:17 +02:00			`max_index: 1`