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
Alternatively, if you have a particularly noisy repository, you can
48
48
instead choose to import all issues excepting it using the
@@ -52,60 +52,60 @@ In this example, ``noisy/repository`` is the repository you would
52
52
*not* like issues created for:
53
53
54
54
.. config::
55
-
:fragment:gitea
55
+
:fragment:forgejo
56
56
57
-
gitea.exclude_repos = noisy/repository
57
+
forgejo.exclude_repos = noisy/repository
58
58
59
59
.. hint::
60
60
If you omit the repository's namespace, bugwarrior will automatically add
61
61
your login as namespace. E.g. the following are equivalent:
62
62
63
63
.. config::
64
-
:fragment:gitea
64
+
:fragment:forgejo
65
65
66
-
gitea.login = foo
67
-
gitea.include_repos = bar
66
+
forgejo.login = foo
67
+
forgejo.include_repos = bar
68
68
69
69
and:
70
70
71
71
.. config::
72
-
:fragment:gitea
72
+
:fragment:forgejo
73
73
74
-
gitea.login = foo
75
-
gitea.include_repos = foo/bar
74
+
forgejo.login = foo
75
+
forgejo.include_repos = foo/bar
76
76
77
77
Alternatively, you can use project IDs instead of names by prefixing the
78
78
project id with `id:`:
79
79
80
80
.. config::
81
-
:fragment:gitea
81
+
:fragment:forgejo
82
82
83
-
gitea.include_repos = id:1234,id:3141
83
+
forgejo.include_repos = id:1234,id:3141
84
84
85
85
Import Labels as Tags
86
86
+++++++++++++++++++++
87
87
88
-
The gitea issue tracker allows you to attach labels to issues; to
88
+
The forgejo issue tracker allows you to attach labels to issues; to
89
89
use those labels as tags, you can use the ``import_labels_as_tags``
90
90
option:
91
91
92
92
.. config::
93
-
:fragment:gitea
93
+
:fragment:forgejo
94
94
95
-
gitea.import_labels_as_tags = True
95
+
forgejo.import_labels_as_tags = True
96
96
97
97
Also, if you would like to control how these labels are created, you can
98
-
specify a template used for converting the gitea label into a Taskwarrior
98
+
specify a template used for converting the forgejo label into a Taskwarrior
99
99
tag.
100
100
101
-
For example, to prefix all incoming labels with the string 'gitea_' (perhaps
101
+
For example, to prefix all incoming labels with the string 'forgejo_' (perhaps
102
102
to differentiate them from any existing tags you might have), you could
103
103
add the following configuration option:
104
104
105
105
.. config::
106
-
:fragment:gitea
106
+
:fragment:forgejo
107
107
108
-
gitea.label_template = gitea_{{label}}
108
+
forgejo.label_template = forgejo_{{label}}
109
109
110
110
In addition to the context variable ``{{label}}``, you also have access
111
111
to all fields on the Taskwarrior task if needed:
@@ -117,33 +117,33 @@ to all fields on the Taskwarrior task if needed:
117
117
118
118
Limit Issues Imported
119
119
+++++++++++++++++++++
120
-
Gitea lets system administrators configure the amount of objects that any given API request will return.
121
-
You may configure the amount to tell Gitea to give to you using the ``issue_limit`` option:
120
+
Forgejo lets system administrators configure the amount of objects that any given API request will return.
121
+
You may configure the amount to tell Forgejo to give to you using the ``issue_limit`` option:
122
122
123
123
.. config::
124
-
:fragment:gitea
124
+
:fragment:forgejo
125
125
126
-
gitea.issue_limit = 200
126
+
forgejo.issue_limit = 200
127
127
128
-
Do note, this will not overwrite what the gitea instance limits you to, it merely lets you set the amount of issues you will import.
128
+
Do note, this will not overwrite what the forgejo instance limits you to, it merely lets you set the amount of issues you will import.
129
129
130
130
131
131
Including various types of issues
132
132
+++++++++++++++++++++
133
133
134
-
Gitea has metadata attached to each issue, primarily: If you are assigned to an issue, if you created an issue, if an issue mentions you, and if an issue has a review reqest for you. You may set if each of these traits is worth importing by using the various ``include_*_issues`` options:
134
+
Forgejo has metadata attached to each issue, primarily: If you are assigned to an issue, if you created an issue, if an issue mentions you, and if an issue has a review reqest for you. You may set if each of these traits is worth importing by using the various ``include_*_issues`` options:
135
135
136
136
.. config::
137
-
:fragment:gitea
137
+
:fragment:forgejo
138
138
139
-
gitea.include_assigned_issues = true
140
-
gitea.include_created_issues = true
141
-
gitea.include_mentioned_issues = true
142
-
gitea.include_review_requested_issues = true
139
+
forgejo.include_assigned_issues = true
140
+
forgejo.include_created_issues = true
141
+
forgejo.include_mentioned_issues = true
142
+
forgejo.include_review_requested_issues = true
143
143
144
144
Each setting will query the API for that trait alone and then add it to your Taskwarrior task list. For example, if you have created issues and mentioned issues off, but assigned issues and review requested issues on: You will only recieve new tasks for the issues you are assigned to do or requested to review, but not for issues you've created or mentioned. Issues that have been assigned to you and created by you would be included though, as these settings merely mark inclusion, not exclusion.
0 commit comments