Option to only ignore fork activity that happened prior to forking (alternative to --skip-fork)

[timotree3]

I'm working with a company that uses repoXplorer to show their development activity.

For their use-case, they don't want to ignore forks entirely, (i.e. using repoxplorer-github-organization --skip-fork), rather, they want to show the activity from their fork, but only the activity that they did, (probably by skipping activity that happened before they forked the repo).

The new option could be called something like --skip-pre-fork-activity.

Does this sound feasible?

P.S. Don't worry, we're planning to add something to the page saying that it's generated by repoXplorer :)

[timotree3]

By the way, I'd be totally excited to take this on, I just don't know where to start. If anyone can give some suggestions to get me started I would be very grateful.

[morucci]

Hello Timo,

Yes I saw that custom deployment of repoXplorer, I'm glad your company is using it and yes obliviously a link to repoXplorer + a statement telling its generated with repoXplorer will be greatly appreciated :)

Regarding your use case, the easiest path o implement this is the use of the date filter from the API. repoxplorer-github-organization is just a simple tool to query the Gihub API to get some basic information about the repositories from an organization. This tool create a configuration file for repoXplorer and nothing more. So simply use it w/o the option -skip-fork. Also the file could created manually, the format is described here: https://github.com/morucci/repoxplorer#define-projects-to-index

So I think it does not require any change to repoXplorer, Instead you should index both non-forked and forked repositories then take advantage of the repoXplorer API to discover the date of the last change of the non-forked one and then query stats about the forked one using the "dfrom" param: https://github.com/morucci/repoxplorer#optionals by setting it at the date of the last change of the non-fork repository. There is only a day resolution that might (if the fork is really active) miss some commits (we can think to improve dfrom/dto to handle second resolution).

I hope it helps, let me know.

[timotree3]

@morucci thanks! I'll look into that approach. I expect that the day resolution won't be a problem for my use-case because it's probably fine to round earlier and over-count by a little.