Re: Harvesting Tips from GitHub

On Thursday, January 25, 2018 at 7:08:45 PM UTC-6, Edward K. Ream wrote: > adding =n to the url gets pages in order. However, it's not clear to me how to detect the last page. Rev aad11fa shows how. It's just a bit tricky. @button get-issues is worth the effort. It checks and complements my

Re: Harvesting Tips from GitHub

On Thursday, January 25, 2018 at 6:11:31 PM UTC-6, Edward K. Ream wrote: > This page discusses "why am I not seeing all my results". Which is fine, except I don't see any way to ask for the next page ;-)

Re: Harvesting Tips from GitHub

On Thursday, January 25, 2018 at 6:00:16 PM UTC-6, Edward K. Ream wrote: > > > This page > > > discusses "why am I not seeing all my results". Which is fine, except I > don't see any way to ask for the next

Re: Harvesting Tips from GitHub

On Thursday, January 25, 2018 at 5:47:06 PM UTC-6, Edward K. Ream wrote: > ...only 30 bugs and 13 enhancements are ever downloaded... This page discusses "why am I not seeing all my results". Which is fine,

Re: Harvesting Tips from GitHub

On Thursday, January 25, 2018 at 1:42:17 PM UTC-6, Edward K. Ream wrote: Recent revs have added @button get-issues to LeoDocs.leo. Alas, not all > Bugs and Enhancements were downloaded, and then rate-limiting is in effect. > Rate limiting no longer seems to be an issue, but only 30 bugs and 13

Re: Harvesting Tips from GitHub

On Wednesday, December 6, 2017 at 5:04:21 PM UTC-6, Terry Brown wrote: > > If we use the "open Tip issues are being edited, closed Tip issues are > ready to use" workflow, we can get the Tips from: > > > https://api.github.com/repos/leo-editor/leo-editor/issues?labels=Tip=closed > > > It's a

Re: Harvesting Tips from GitHub

On Wed, Dec 6, 2017 at 5:04 PM, Terry Brown wrote: > If we use the "open Tip issues are being edited, closed Tip issues are > ready to use" workflow, we can get the Tips from: > > https://api.github.com/repos/leo-editor/leo-editor/issues? > labels=Tip=closed > > It's a

Re: Harvesting Tips from GitHub

On Thursday, December 7, 2017 at 2:28:52 PM UTC-3, Terry Brown wrote: > 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 >

Re: Harvesting Tips from GitHub

On Thu, 7 Dec 2017 09:11:49 -0800 (PST) "Xavier G. Domingo (xgid)" 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 >

Re: Harvesting Tips from GitHub

On Thursday, December 7, 2017 at 1:20:07 PM UTC-3, Terry Brown wrote: > > > I disagree. We need to define the canonical source for the tips, or > violate DRY. If we're using GitHub because of its markdown editing / > preview, I think by default GitHub is the canonical source. > > I agree

Re: Harvesting Tips from GitHub

On Thu, 7 Dec 2017 06:30:13 -0600 "Edward K. Ream" wrote: > On Wed, Dec 6, 2017 at 5:04 PM, Terry Brown > wrote: > > > If we use the "open Tip issues are being edited, closed Tip issues > > are ready to use" workflow, we can get the Tips from: > > >

Re: Harvesting Tips from GitHub

On Wed, Dec 6, 2017 at 5:04 PM, Terry Brown wrote: > If we use the "open Tip issues are being edited, closed Tip issues are > ready to use" workflow, we can get the Tips from: > > https://api.github.com/repos/leo-editor/leo-editor/issues? > labels=Tip=closed > > It's a

Harvesting Tips from GitHub

If we use the "open Tip issues are being edited, closed Tip issues are ready to use" workflow, we can get the Tips from: https://api.github.com/repos/leo-editor/leo-editor/issues?labels=Tip=closed It's a JSON list of dicts which have a `body` key (they ripped that terminology off Leo, I bet ;-)