Bug Squad Issue Comments/it: Difference between revisions
From Joomla! Documentation
Created page with "= Testi di esempio =" |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
Testo predefinito per i membri della comunità per aggiornare un problema in assenza di commenti/azioni. | Testo predefinito per i membri della comunità per aggiornare un problema in assenza di commenti/azioni. | ||
= Testi di esempio = | = Testi di esempio = | ||
'' | ''Sostituisci i testi all'interno delle parentesi <tt>[]</tt> con i valori appropriati.''<br /> | ||
Leggenda: | |||
* <tt>[username]</tt>: Use the "github username" of the creator like @zero-24 to notify them, look at the first entry to find out who created the issue. | * <tt>[username]</tt>: Use the "github username" of the creator like @zero-24 to notify them, look at the first entry to find out who created the issue. | ||
* <tt>[date]</tt>: The date of when the last comment was made in the issue. | * <tt>[date]</tt>: The date of when the last comment was made in the issue. | ||
| Line 35: | Line 35: | ||
'''Tip:''' If we have such issues/pull requests a CMS Maintainer can add the '''Test instructions missing''' label on GitHub. Please ping [http://volunteers.joomla.org/working-groups/cms-maintenance-team one of them] e.g. via GitHub Notification. | '''Tip:''' If we have such issues/pull requests a CMS Maintainer can add the '''Test instructions missing''' label on GitHub. Please ping [http://volunteers.joomla.org/working-groups/cms-maintenance-team one of them] e.g. via GitHub Notification. | ||
== | == Un problema con i conflitti di fusione == | ||
<pre> | <pre> | ||
| Line 49: | Line 49: | ||
</pre> | </pre> | ||
== | == Chiudere un problema perché non è stata ricevuta alcuna risposta == | ||
<pre> | <pre> | ||
| Line 63: | Line 63: | ||
__NOTOC__ | __NOTOC__ | ||
<noinclude> | <noinclude> | ||
[[Category:Bug Squad]] | [[Category:Bug Squad/it|Bug Squad]] | ||
[[Category:Bug Tracker]] | [[Category:Bug Tracker/it|Bug Tracker]] | ||
[[Category:Core Contributions]] | [[Category:Core Contributions/it|Core Contributions]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 17:40, 3 December 2021
Testo predefinito per i membri della comunità per aggiornare un problema in assenza di commenti/azioni.
Testi di esempio
Sostituisci i testi all'interno delle parentesi [] con i valori appropriati.
Leggenda:
- [username]: Use the "github username" of the creator like @zero-24 to notify them, look at the first entry to find out who created the issue.
- [date]: The date of when the last comment was made in the issue.
Normal (Pull request is mergeable and has test instructions)
Hello @[username] Thank you for your contribution. The last comment here was on [date]. So the question is, Is this issue/pull request still valid? If no reply is received within 4 weeks we will close this issue. Thanks for understanding!
An issue without test instructions
Hello @[username] Thank you for your contribution. The last comment here was on [date]. So the question is, Is this issue/pull request still valid? if so please provide clear test instructions to be able to test / reproduce this issue. If no reply is received within 4 weeks we will close this issue. Thanks for understanding!
Tip: If we have such issues/pull requests a CMS Maintainer can add the Test instructions missing label on GitHub. Please ping one of them e.g. via GitHub Notification.
Un problema con i conflitti di fusione
Hello @[username] Thank you for your contribution. The last comment here was on [date]. So the question is, Is this issue/pull request still valid? If the issue is still valid can you please rebase to the current staging or re-do the PR so we are able to merge. If no reply is received within 4 weeks we will close this issue. Thanks for understanding!
Chiudere un problema perché non è stata ricevuta alcuna risposta
Hello @[username] Thank you for your contribution. As no reply has been received within the past 4 weeks, the issue is being closed. Feel free to re-open the issue any time when you are ready to work on it further. Thanks for understanding!