lavelle

Hi HN,

I've been working on an app for tracking refactors and code migrations recently. I got the idea at my last job where we always had lots of these migrations going on at once (for example, moving from Angular to React, or moving from Flow to Typescript). We would track how many files still needed to be migrated by grepping for certain files and pasting the results into a spreadsheet.

This seemed inefficient, and like it was a problem that other companies or open source projects might be having. I built an MVP, but I wanted to see if this was a problem other people had faced, or if there was any need for a product like this, before going much further.

Let me know if you have any questions or feedback!

Hey everyone, OP here. Let me know if you have any questions or feedback. It's an early MVP, but I wanted to get some more people trying it to see how well it works for real repositories. Back at my old job we had a big spreadsheet for tracking all the in progress code migrations (such as moving from Angular to React) which we would update manually by running grep commands, etc. to find the number of remaining instances. I thought there might be some demand for a product solution.

Right now it updates once an hour and uses the Github API for searching. The next step to make it much more powerful is to build an engine that clones the repo and allows the user to run arbitrary grep or other commands, and run it as a Github hook when new code is merged. This would also allow us to build historical graphs by checking out previous commits.

Hey everyone, creator here. Let me know if you have any questions or feedback. It's an early MVP, but I wanted to get some more people trying it to see how well it works for real repositories.

Back at my old job we had a big spreadsheet for tracking all the in progress code migrations (such as moving from Angular to React) which we would update manually by running grep commands, etc. to find the number of remaining instances. I thought there might be some demand for a product solution.

Right now it updates once an hour and uses the Github API for searching. The next step to make it much more powerful is to build an engine that clones the repo and allows the user to run arbitrary grep or other commands, and run it as a Github hook when new code is merged. This would also allow us to build historical graphs by checking out previous commits.

I think I'll keep Ctrl+D for quitting the whole program, Ctrl+C for just finishing the REPL and going to the save/discard prompt.

I love the idea of Jason Derulo becoming aware of the existence of a Node.js module.

Nice idea. That could definitely explain things faster than a description of it. I'll make one this afternoon.

Fixed now. Just type Ctrl-C. Thanks for the report.