On Thu, 7 Dec 2017 09:11:49 -0800 (PST) "Xavier G. Domingo (xgid)" <[email protected]> wrote:
> > If a tip needs revision (they will), where does that happen? > > It could be done in many ways, but one could be storing the > "closed_at" date somehow in our "harvested" copy and comparing it > with the current "closed_at" date of the tip at each harvest. To make > a revision, we should simply *Reopen *the issue at GitHub and *Close > *it again when the new text is in place. What do you think? I think the current GitHub solution handles revision. The harvesting code only takes a moment to run - we could add it to a git commit hook as a once a day thing for example. As you say re-opening an tip-issue could be used to temporarily exclude it from harvesting, if needed. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
