4

After posting my thoughs on Should debugging CI/CD problems caused by coding errors in the software product itself be on-topic? it comes to my mind we need some usual 'off-topic' close reasons on top of the 2 actually present:

enter image description here

So add an answer with the close reason text as quote and the reasoning behind your proposition with how and when it should be used.
We, moderators, do keep the right to not include a reason whatever the votes are if we think it would be toxic for the site, in this case a meta post would be raised to explain the reasons.

2
  • 1
    You might also want to define the help center page linked in the first close reason (time for a different meta post, maybe?)
    – Aurora0001
    Apr 6 '17 at 9:49
  • 1
    @Aurora0001 I've think of it, I do hope this post will lead to starting material for this page indeed :)
    – Tensibai
    Apr 6 '17 at 9:49
4

Quoted from Stack Overflow reasons, trimmed for devops:

This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers.

This reason is quite self explanatory but I think it should be used when the solution was found in comments and doesn't deserve an answer which would solve someone else time later. For example: a simple typo error in a command or a quote missing, when resolved by 1 or 2 comments would fit.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .