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
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
Below the question is a "promoted" answer that is designated as the Approved Solution
The original ordering of all responses should stay in tact, so that everyone can see where and when the Approved Solution originally appeared.
Consider making the "Approved Solution" a simple link, with the same text across all repositories. IE: you don't actually duplicate the solution in a box below the question, you simply link to the Approved Solution. It might look like this:
"There is a response to this issue that has been marked as a Solution."
You could even go crazy and give both the repo owner and the person asking the Issue permission to mark it as approved. Like this:
"There is a response to this issue that has been marked as a Solution."
The owner of this repo marked this response as the solution
The person that opened the issued marked this other response as the solution
The text was updated successfully, but these errors were encountered:
Inspiration for this idea was birthed here. In this example, the issue was opened in September of 2014. It was closed then re-opened. It is now closed. As of today (May 2016) there is still activity as recent as 8 hours ago.
Think how much time is lost scrubbing through this issue when an answer might be known by both parties.
This is such an essential and basic feature. How often do you browse a closed issue (for example a feature request) and have to skim through 154 comments to find out:
if is has been implemented or not
In which release
What the API looks like
I have to do this all the time. Instead of just marking a comment as the solution I propose that closing an issue also prompts for an optional summary/reason, which is then displayed at the top. It could answer all the questions above and also summarize the process that lead to it.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
You could even go crazy and give both the repo owner and the person asking the Issue permission to mark it as approved. Like this:
The text was updated successfully, but these errors were encountered: