The reason for the rejection was that Freerse's GitHub repository lacked development and update records. This was because the development had previously been done locally. The code was only uploaded to GitHub when applying for funding.

Replies (6)

Moss, just do that. Start committing a bunch of small changes and reapply. This is the type of hoop jumping that has to be done in the fiat world to get around nonsense regs. Ironically very similar vibes here.
Should make a commit announcing the completion of a feature, but then over the course of 6 months every day commit again. Each commit is a bug fix and slightly obfuscates your code, with each commit being a small patch becoming reading more haggered and despaired. At the end, the commit messages just read "please work, just this once" Productivityℒ️
Just because you are developing locally doesn't mean you wouldn't have a large number of commits over a long period of time when you do push it. I don't know how you can build something non-trivial if you aren't doing commits every time you solve a problem. If you don't work this way, how do you step through commits for debugging etc, and how do you checkout a previous commit to figure out where something broke?
↑