Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Users seem to use the [Post your answer] as a reply often

Ouverte
#1,504 5 commentaires 1 réaction 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 4 jours

@fenbox y travaille déjà.

Depuis le 11/3/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

enhancement

Context

I observe that users are often using the [Post your answer] as a reply to an answer, not understanding that this option is to answer a question. E.g. the following happens:

  • User creates new question
  • The question is answered, sometimes requesting for some more feedback if it does not solve the issue.
  • The user has feedback, but instead of using the [Add comment] option, he / she uses the [Post your answer] thinking it is to reply to the previous answer.

I think the reason is because the Your Answer form is immediately displayed, where the [Add comment] option requires an additional click to show the form. Thus users are missing that they are using the wrong form.

Examples:

Describe the solution you'd like

Maybe an additional check should be added when the user of the question is the same as the user trying to press the [Post your answer]. Something like Only use this field to answer your own question. To reply to an answer please use the [Add comment] button.

Alternatively, maybe it should be made a bit "harded" to self-answer a question. E.g. when the user of the question and the user trying to answer is the same, do not show the Your Answer form but add a Button to expand it + making the user aware that it should only be used to answer the question, not to reply.

Langage dominant
Go
Étoiles
15.7k
Forks
1.4k
Merge moyen
1 j 12 h
PR mergées (30 j)
2

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/answer

Toutes les issues de apache/answer

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.