On 2018-01-05 13:00, Erik Bray wrote: > On Thu, Jan 4, 2018 at 10:26 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> > wrote: >> On 2018-01-02 22:59, Volker Braun wrote: >>> >>> IMHO it shouldn't be easy to find. Certainly nobody should base their >>> work on it. >> >> >> I agree here. > > I don't, but I also seem to recall you linking me to it after I > complained about it being "secret" as if it were somehow obvious to > find. This is what I meant by "secret"--perhaps a bit glib because > it's not secret like a password, but certainly obscured...
I am not sure how automatic the releasemanager workflow of try merging a ticket and setting a ticket to needs_work if not successful is. But in the case this works automatically, would it be possible to, after setting it to needs_work, post the output of #!/bin/bash TAG=`git describe --abbrev=0 --first-parent` echo `git log --pretty=format:'%s' --first-parent $TAG.. | sed -r 's|.*(#[0-9]+).*|\1|'` $TAG as a comment on the ticket. This return something like #24389 #24384 #24383 #24382 #24300 #24214 #23399 8.2.beta1 which gives a glue where to search. Best Daniel -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
