You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* giteaofficial/main:
Scoped label display and documentation tweaks (go-gitea#23430)
Deduplicate template code for label selection menu (go-gitea#23431)
Show edit/close/delete button on organization wide repositories (go-gitea#23388)
Sync the class change of Edit Column Button to JS code (go-gitea#23400)
Preserve file size when creating attachments (go-gitea#23406)
[skip ci] Updated translations via Crowdin
Use buildkit for docker builds (go-gitea#23415)
Refactor branch/tag selector dropdown (first step) (go-gitea#23394)
[skip ci] Updated translations via Crowdin
Hide target selector if tag exists when creating new release (go-gitea#23171)
Parse external request id from request headers, and print it in access log (go-gitea#22906)
Add missing tabs to org projects page (go-gitea#22705)
Add user webhooks (go-gitea#21563)
Handle OpenID discovery URL errors a little nicer when creating/editing sources (go-gitea#23397)
Split CI pipelines (go-gitea#23385)
Copy file name to clipboardexpand all lines: docs/content/doc/advanced/config-cheat-sheet.en-us.md
+6
Original file line number
Diff line number
Diff line change
@@ -881,7 +881,13 @@ Default templates for project boards:
881
881
-`Identity`: the SignedUserName or `"-"` if not logged in.
882
882
-`Start`: the start time of the request.
883
883
-`ResponseWriter`: the responseWriter from the request.
884
+
-`RequestID`: the value matching REQUEST_ID_HEADERS(default: `-`, if not matched).
884
885
- You must be very careful to ensure that this template does not throw errors or panics as this template runs outside of the panic/recovery script.
886
+
-`REQUEST_ID_HEADERS`: **\<empty\>**: You can configure multiple values that are splited by comma here. It will match in the order of configuration, and the first match will be finally printed in the access log.
887
+
- e.g.
888
+
- In the Request Header: X-Request-ID: **test-id-123**
889
+
- Configuration in app.ini: REQUEST_ID_HEADERS = X-Request-ID
Copy file name to clipboardexpand all lines: docs/content/doc/usage/labels.en-us.md
+3-5
Original file line number
Diff line number
Diff line change
@@ -23,17 +23,15 @@ For repositories, labels can be created by going to `Issues` and clicking on `La
23
23
24
24
For organizations, you can define organization-wide labels that are shared with all organization repositories, including both already-existing repositories as well as newly created ones. Organization-wide labels can be created in the organization `Settings`.
25
25
26
-
Labels have a mandatory name, a mandatory color, an optional description, and must either be exclusive or not (see `Scoped labels` below).
26
+
Labels have a mandatory name, a mandatory color, an optional description, and must either be exclusive or not (see `Scoped Labels` below).
27
27
28
28
When you create a repository, you can ensure certain labels exist by using the `Issue Labels` option. This option lists a number of available label sets that are [configured globally on your instance](../customizing-gitea/#labels). Its contained labels will all be created as well while creating the repository.
29
29
30
30
## Scoped Labels
31
31
32
-
A scoped label is a label that contains `/` in its name (not at either end of the name). For examplelabels `kind/bug` and `kind/enhancement`both have scope `kind`. Such labels will display the scope with slightly darker color.
32
+
Scoped labels are used to ensure at most a single label with the same scope is assigned to an issue or pull request. For example, if labels `kind/bug` and `kind/enhancement` have the Exclusive option set, an issue can only be classified as a bug or an enhancement.
33
33
34
-
The scope of a label is determined based on the **last**`/`, so for example the scope of label `scope/subscope/item` is `scope/subscope`.
35
-
36
-
Scoped labels can be marked as exclusive. This ensures at most a single label with the same scope is assigned to an issue or pull request. For example, if `kind/bug` and `kind/enhancement` are marked exclusive, an issue can only be classified as a bug or an enhancement.
34
+
A scoped label must contain `/` in its name (not at either end of the name). The scope of a label is determined based on the **last**`/`, so for example the scope of label `scope/subscope/item` is `scope/subscope`.
0 commit comments