-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better Code Hub #101
Comments
Nice, I like these ten guidelines a lot; they're more high-level architectural aspects rather than the usual linting fare. Although when I tried it on my repo, the analysis seems a bit simplistic in some cases. And it fails me on not keeping my unit interfaces small, but that's mainly in generated code :-). Disclaimer: not entirely unbiased, as SIG reviewed the NDFF architecture and backed me up on it after there were some issues :-). My impression of them is that they really know their stuff however (the swanky office in the Rembrandt Tower helps of course). |
The service at https://bettercodehub.com/ requires write permission on your GitHub repositories including the code. In their terms they promise to only make a copy of the code. Think carefully before granting the permission. |
So why to they need write permission then? Perhaps submit an issue? |
For setting up webhooks see https://bettercodehub.com/docs/faq question 4.4. |
This content would be more appropriate for The Turing Way |
Last week during ICTOpen, I spoke with someone from SIG (software improvement group, not special interest group). They've developed their The 10 Guidelines for Maintainable Software, and have tool which checks your github repo to assess how maintainable id your code.
It looks interesting -- maybe it is just yet another code quality tool. But maybe it is worth checking it out! If it turns out to be quite good, maybe we can include it in the guide?
The text was updated successfully, but these errors were encountered: