3 ms·
> The complaint is that it's come up repeatedly ('Not again. Use search') - agree it's a bit of a brush off, and it's not helpful for anybody (perhaps most of a
by stavros 5y ago
> The complaint is that it's come up repeatedly ('Not again. Use search') - agree it's a bit of a brush off, and it's not helpful for anybody (perhaps most of all the maintainers themselves!) that it doesn't link any of the others, or the one that was merged, or the first one with a better explanation for rejection, or whatever.
I love using automation for this. I'm often frustrated that people didn't bother searching, and I don't have enough time in the day to do the searching for them. I configure my repos so that I can just apply the "duplicate" label, and a bot will leave a polite and cheerful message thanking people and asking them to search next time to avoid duplicates.
It successfully fails to evoke my exact mental state at the moment and gives people the exact info and reasons for rejection they need, all without me having to lift a finger.
- DarylZero 5y agoIn this case the software could be automated to shorten the name without even showing the user the error. Or the error message could provide, in its output, a documented option to shorten the name (e.g. --truncate-filenames). This seems a better use of automation than nuking user reports about the error.