Make tuttle work with very active repos that are deployed into a subcollection

[DrRataplan]

• Change front-end to send the collection uri-encoded. Roaster will decode that before calling the handler. Makes working with subcollections possible
• Search for a commit over multiple pages, up to 500 total commits. This makes upgrades over multiple pages work.

[line-o]

Thanks for taking the time to add a test for this important feature.
I think it is worth to give the stop-condition parameter another thought.

Is it necessary to recheck all previous results? There might be legit reasons like number of all commits read, but this hard-limit is handled elsewhere as I understand the code.

I think I would prefer github:get-raw-commits to accept the stop-condition as a function. That has more re-use potential than to limit it to just until-sha.
What do you think?

[DrRataplan]

Thanks for taking the time to add a test for this important feature. I think it is worth to give the stop-condition parameter another thought.

Is it necessary to recheck all previous results? There might be legit reasons like number of all commits read, but this hard-limit is handled elsewhere as I understand the code.

I think I would prefer github:get-raw-commits to accept the stop-condition as a function. That has more re-use potential than to limit it to just until-sha. What do you think?

Not sure whether I agree. it's a simple refactoring if we do need it. I'd rather do it when we need it instead of making this code more complex to be honest.

[line-o]

LGTM!