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
* upstream/main:
[skip ci] Updated translations via Crowdin
Update JS and PY dependencies (go-gitea#28120)
Decrease issue font size in project template (go-gitea#28054)
Require clear descriptions both for feature and breaking PRs prior to the merge (go-gitea#28112)
add skip ci functionality (go-gitea#28075)
Fix project counter in organization/individual profile (go-gitea#28068)
Fix Show/hide filetree button on small displays (go-gitea#27881)
Change default size of attachments and repo files (go-gitea#28100)
Fix Matrix and MSTeams nil dereference (go-gitea#28089)
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+18-5Lines changed: 18 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -203,10 +203,20 @@ Some of the key points:
203
203
204
204
In the PR title, describe the problem you are fixing, not how you are fixing it. \
205
205
Use the first comment as a summary of your PR. \
206
-
In the PR summary, you can describe exactly how you are fixing this problem. \
206
+
In the PR summary, you can describe exactly how you are fixing this problem.
207
+
207
208
Keep this summary up-to-date as the PR evolves. \
208
209
If your PR changes the UI, you must add **after** screenshots in the PR summary. \
209
-
If you are not implementing a new feature, you should also post **before** screenshots for comparison. \
210
+
If you are not implementing a new feature, you should also post **before** screenshots for comparison.
211
+
212
+
If you are implementing a new feature, your PR will only be merged if your screenshots are up to date.\
213
+
Furthermore, feature PRs will only be merged if their summary contains a clear usage description (understandable for users) and testing description (understandable for reviewers).
214
+
You should strive to combine both into a single description.
215
+
216
+
Another requirement for merging PRs is that the PR is labeled correctly.\
217
+
However, this is not your job as a contributor, but the job of the person merging your PR.\
218
+
If you think that your PR was labeled incorrectly, or notice that it was merged without labels, please let us know.
219
+
210
220
If your PR closes some issues, you must note that in a way that both GitHub and Gitea understand, i.e. by appending a paragraph like
211
221
212
222
```text
@@ -255,13 +265,16 @@ Changing the default value of a setting or replacing the setting with another on
255
265
256
266
#### How to handle breaking PRs?
257
267
258
-
If your PR has a breaking change, you must add a `BREAKING` section to your PR summary, e.g.
268
+
If your PR has a breaking change, you must add two things to the summary of your PR:
259
269
260
-
```
270
+
1. A reasoning why this breaking change is necessary
271
+
2. A `BREAKING` section explaining in simple terms (understandable for a typical user) how this PR affects users and how to mitigate these changes. This section can look for example like
272
+
273
+
```md
261
274
## :warning: BREAKING :warning:
262
275
```
263
276
264
-
To explain how this will affect users and how to mitigate these changes.
277
+
Breaking PRs will not be merged as long as not both of these requirements are met.
Copy file name to clipboardExpand all lines: docs/content/administration/config-cheat-sheet.en-us.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1396,6 +1396,7 @@ PROXY_HOSTS = *.github.com
1396
1396
-`ZOMBIE_TASK_TIMEOUT`: **10m**: Timeout to stop the task which have running status, but haven't been updated for a long time
1397
1397
-`ENDLESS_TASK_TIMEOUT`: **3h**: Timeout to stop the tasks which have running status and continuous updates, but don't end for a long time
1398
1398
-`ABANDONED_JOB_TIMEOUT`: **24h**: Timeout to cancel the jobs which have waiting status, but haven't been picked by a runner for a long time
1399
+
-`SKIP_WORKFLOW_STRINGS`: **[skip ci],[ci skip],[no ci],[skip actions],[actions skip]**: Strings committers can place inside a commit message to skip executing the corresponding actions workflow
1399
1400
1400
1401
`DEFAULT_ACTIONS_URL` indicates where the Gitea Actions runners should find the actions with relative path.
1401
1402
For example, `uses: actions/checkout@v3` means `https://github.com/actions/checkout@v3` since the value of `DEFAULT_ACTIONS_URL` is `github`.
projects.column.set_default_desc=Missionne cette colonne d'accueillir les tickets et demande d'ajouts noncatégorisés.
1333
+
projects.column.set_default_desc=Les tickets et demandes d’ajout non-catégorisés seront placés dans cette colonne.
1334
1334
projects.column.unset_default=Défaire par défaut
1335
-
projects.column.unset_default_desc=Décharge cette colonne d'accueillir les tickets et demandes d'ajouts non catégorisées. Ceux-ci iront dans une colonne idoine.
1335
+
projects.column.unset_default_desc=Les tickets et demandes d'ajouts non-catégorisés seront placés dans une colonne idoine.
1336
1336
projects.column.delete=Supprimer la colonne
1337
1337
projects.column.deletion_desc=La suppression d'une colonne de projet déplace tous les tickets liés à 'Non catégorisé'. Continuer ?
1338
1338
projects.column.color=Couleur
@@ -3214,22 +3214,22 @@ notices.delete_success=Les informations systèmes ont été supprimées.
3214
3214
3215
3215
[action]
3216
3216
create_repo=a créé le dépôt <a href="%s">%s</a>
3217
-
rename_repo=a rebaptisé le dépôt de <code>%[1]s</code> vers <a href="%[2]s">%[3]s</a>
3218
-
commit_repo=a soumis sur <a href="%[2]s">%[3]s</a> à <a href="%[1]s">%[4]s</a>
0 commit comments