mirror of
https://github.com/go-gitea/gitea
synced 2024-11-10 20:24:24 +00:00
8d99ee2773
* Add organization wide labels Implement organization wide labels similar to organization wide webhooks. This lets you create individual labels for organizations that can be used for all repos under that organization (so being able to reuse the same label across multiple repos). This makes it possible for small organizations with many repos to use labels effectively. Fixes #7406 * Add migration * remove comments * fix tests * Update options/locale/locale_en-US.ini Removed unused translation string * show org labels in issue search label filter * Use more clear var name * rename migration after merge from master * comment typo * update migration again after rebase with master * check for orgID <=0 per guillep2k review * fmt * Apply suggestions from code review Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> * remove unused code * Make sure RepoID is 0 when searching orgID per code review * more changes/code review requests * More descriptive translation var per code review * func description/delete comment when issue label deleted instead of hiding it * remove comment * only use issues in that repo when calculating number of open issues for org label on repo label page * Add integration test for IssuesSearch API with labels * remove unused function * Update models/issue_label.go Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> * Use subquery in GetLabelIDsInReposByNames * Fix tests to use correct orgID * fix more tests * IssuesSearch api now uses new BuildLabelNamesIssueIDsCondition. Add a few more tests as well * update comment for clarity * Revert previous code change now that we can use the new BuildLabelNamesIssueIDsCondition * Don't sort repos by date in IssuesSearch API After much debugging I've found a strange issue where in some cases MySQL will return a different result than other enigines if a query is sorted by a null collumn. For example with our integration test data where we don't set updated_unix in repository fixtures: SELECT `id`, `owner_id`, `owner_name`, `lower_name`, `name`, `description`, `website`, `original_service_type`, `original_url`, `default_branch`, `num_watches`, `num_stars`, `num_forks`, `num_issues`, `num_closed_issues`, `num_pulls`, `num_closed_pulls`, `num_milestones`, `num_closed_milestones`, `is_private`, `is_empty`, `is_archived`, `is_mirror`, `status`, `is_fork`, `fork_id`, `is_template`, `template_id`, `size`, `is_fsck_enabled`, `close_issues_via_commit_in_any_branch`, `topics`, `avatar`, `created_unix`, `updated_unix` FROM `repository` ORDER BY updated_unix DESC LIMIT 15 OFFSET 45 Returns different results for MySQL than other engines. However, the similar query: SELECT `id`, `owner_id`, `owner_name`, `lower_name`, `name`, `description`, `website`, `original_service_type`, `original_url`, `default_branch`, `num_watches`, `num_stars`, `num_forks`, `num_issues`, `num_closed_issues`, `num_pulls`, `num_closed_pulls`, `num_milestones`, `num_closed_milestones`, `is_private`, `is_empty`, `is_archived`, `is_mirror`, `status`, `is_fork`, `fork_id`, `is_template`, `template_id`, `size`, `is_fsck_enabled`, `close_issues_via_commit_in_any_branch`, `topics`, `avatar`, `created_unix`, `updated_unix` FROM `repository` ORDER BY updated_unix DESC LIMIT 15 OFFSET 30 Returns the same results. This causes integration tests to fail on MySQL in certain cases but would never show up in a real installation. Since this API call always returns issues based on the optionally provided repo_priority_id or the issueID itself, there is no change to results by changing the repo sorting method used to get ids earlier in the function. * linter is back! * code review * remove now unused option * Fix newline at end of files * more unused code * update to master * check for matching ids before query * Update models/issue_label.go Co-Authored-By: 6543 <6543@obermui.de> * Update models/issue_label.go * update comments * Update routers/org/setting.go Co-authored-by: Lauris BH <lauris@nix.lv> Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com> Co-authored-by: 6543 <6543@obermui.de> |
||
|---|---|---|
| .. | ||
| migrations.go | ||
| v70.go | ||
| v71.go | ||
| v72.go | ||
| v73.go | ||
| v74.go | ||
| v75.go | ||
| v76.go | ||
| v77.go | ||
| v78.go | ||
| v79.go | ||
| v80.go | ||
| v81.go | ||
| v82.go | ||
| v83.go | ||
| v84.go | ||
| v85.go | ||
| v86.go | ||
| v87.go | ||
| v88.go | ||
| v89.go | ||
| v90.go | ||
| v91.go | ||
| v92.go | ||
| v93.go | ||
| v94.go | ||
| v95.go | ||
| v96.go | ||
| v97.go | ||
| v98.go | ||
| v99.go | ||
| v100.go | ||
| v101.go | ||
| v102.go | ||
| v103.go | ||
| v104.go | ||
| v105.go | ||
| v106.go | ||
| v107.go | ||
| v108.go | ||
| v109.go | ||
| v110.go | ||
| v111.go | ||
| v112.go | ||
| v113.go | ||
| v114.go | ||
| v115.go | ||
| v116.go | ||
| v117.go | ||
| v118.go | ||
| v119.go | ||
| v120.go | ||
| v121.go | ||
| v122.go | ||
| v123.go | ||
| v124.go | ||
| v125.go | ||
| v126.go | ||
| v127.go | ||
| v128.go | ||
| v129.go | ||
| v130.go | ||
| v131.go | ||
| v132.go | ||
| v133.go | ||
| v134.go | ||
| v135.go | ||