On Tue, Sep 26, 2023 at 07:19:46AM -0700, Junio C Hamano wrote: > At the same time, it would be one less thing they need to tweak > before starting to use it, and if there are two or more users to do > so, it would already have paid off. Developers typically outnumber > projects they work on. > > I also have to wonder if it might make it more obvious what is going > on if you made the default to $user/$fork and have the project > override it, which hopefully may make it easier to find out what > they need to do for those who want to override it to a different > value to suit their need? Yeah, that was my thinking (and what I had been proposing). But I really think it probably doesn't matter that much either way. I would not be surprised if there are zero developers who use this, because of the setup on the coverity side, and the fact that the results are not always immediately actionable. Even I, who has been running coverity on my local fork for a few years, will probably just switch to using the git.git run and occasionally looking at the results (that creates an extra headache because somebody has to grant acess to the git.git run results to interested parties, but it's also a one-time setup thing). -Peff
