Replying to Avatar gsovereignty

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?
Avatar
Moss 1mo ago

We actually developed Freerse in a private GitLab repository, and only made the code publicly available on GitHub when applying for OpenSats funding.

Our development workflow included numerous local and private commits, which is why the full development history isn’t visible on GitHub.

The stability and full functionality of the Freerse app, along with real user feedback, are the clearest proof of our continuous development work—even if the commit history wasn’t publicly visible from the start.

Reply to this note

Please Login to reply.

Discussion

No replies yet.