Bug Squad Issue Comments/fr: Difference between revisions

From Joomla! Documentation

← Older edit
MATsxm (talk | contribs)
Email Confirmed, JDOC Contributors, Translator
34,129 edits
Created page with "= Exemple de textes ="
MATsxm (talk | contribs)
Email Confirmed, JDOC Contributors, Translator
34,129 edits
Created page with "== Fermer un rapport d'anomalie pour absence de réponse =="
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<noinclude><languages /></noinclude>
<noinclude><languages /></noinclude>
Default text for Community Members to update an issue there is no comment/action.
Textes par défaut pour que les Membres de la Communauté puissent mettre à jour un rapport d'anomalie qui n'a pas de commentaire/action.
= Exemple de textes =
= Exemple de textes =  
''Replace the texts within the <tt>[]</tt> brackets with the appropriate values.''
''Remplacer les textes à l'intérieur de <tt>[]</tt> par les valeurs appropriées.''<br />
Legenda:
Légende :
* <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> (nom d'utilisateur) : utilisez le le "nom d'utilisateur GitHub" de l'auteur comme par exemple @zero-24 pour les notifier. Consultez la première entrée pour savoir qui a créé le rapport d'anomalie.
* <tt>[date]</tt>: The date of when the last comment was made in the issue.
* <tt>[date]</tt>: la date du dernier commentaire sur le rapport d'anomalie.
== Normal (Pull request is mergable and has testinstructions) ==
== Normal (le Pull Request peut être fusionné et dispose d'instructions pour le test) ==


<pre>
<pre>
Line 19: Line 19:
</pre>
</pre>


== An issue without testinstructions ==
== Un rapport d'anomalie sans instructions de tests ==
   
   
<pre>
<pre>
Line 33: Line 33:
</pre>
</pre>


'''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.
'''Astuce''' : si il existe ce type d'anomalie/Pull Request, un responsable CMS pourra ajouter l'étiquette '''Instructions de test manquantes''' sur GitHub. Veuillez contacter [http://volunteers.joomla.org/working-groups/cms-maintenance-team un des membres de l'équipe], par exemple via les notifications GitHub.


== An issue with merge conflicts ==
== Un rapport d'anomalie avec un conflit de fusion ==
   
   
<pre>
<pre>
Line 45: Line 45:
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 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.
If no reply is received within 4 weeks we will close this issue.
Thanks for understanding!
</pre>
== Fermer un rapport d'anomalie pour absence de réponse ==
<pre>
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!
Thanks for understanding!
Line 51: Line 63:
__NOTOC__
__NOTOC__
<noinclude>
<noinclude>
[[Category:Bug Squad]]
[[Category:Bug Squad/fr|Bug Squad]]
[[Category:Bug Tracker]]
[[Category:Bug Tracker/fr|Bug Tracker]]
[[Category:Core Contributions]]
[[Category:Core Contributions/fr|Contributions au noyau]]
</noinclude>
</noinclude>

Latest revision as of 20:36, 8 November 2015

Other languages:

Textes par défaut pour que les Membres de la Communauté puissent mettre à jour un rapport d'anomalie qui n'a pas de commentaire/action.

Exemple de textes

Remplacer les textes à l'intérieur de [] par les valeurs appropriées.
Légende :

  • [username] (nom d'utilisateur) : utilisez le le "nom d'utilisateur GitHub" de l'auteur comme par exemple @zero-24 pour les notifier. Consultez la première entrée pour savoir qui a créé le rapport d'anomalie.
  • [date]: la date du dernier commentaire sur le rapport d'anomalie.

Normal (le Pull Request peut être fusionné et dispose d'instructions pour le test)

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!

Un rapport d'anomalie sans instructions de tests

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!

Astuce : si il existe ce type d'anomalie/Pull Request, un responsable CMS pourra ajouter l'étiquette Instructions de test manquantes sur GitHub. Veuillez contacter un des membres de l'équipe, par exemple via les notifications GitHub.

Un rapport d'anomalie avec un conflit de fusion

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!

Fermer un rapport d'anomalie pour absence de réponse

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!
Retrieved from "https://docs.sandbox.joomla.org/index.php?title=Bug_Squad_Issue_Comments/fr&oldid=255167"