GitHub repository setup

[gucio321]

Hi @AllenDang
thank you for inviting me to collaborating on this repository!

I've a proposal about setting up a branch-protection-rules.
In my opinion the protection rule should now enforce at least one PR review. This way, one person would give approval, and another one will merge. This will reduce a possibility of merging bugged code to master 😄

we should also add some auto-tests. e.g. a simple workflow file that will run go test ./... to ensure the code isn't buildable

[AllenDang]

Totally agree

[gucio321]

I'd blame #18

ops, sorry, wrong issue 😄

Totally agree

great!, Sadly, I can't do that, since I don't have access to settings, but the setup should look like that:

[gucio321]

very well, so since #45 is already merged, @AllenDang you need to enable rule for this check
and could you also check this "Require branches to be up-to-data..." - it makes "Update branch" button appear and it's easier to update branch fro github's UI 😄

[eliasdaler]

Another proposal: let's enable "Discussions" in this repo and move topics like these there instead of making many "issues" as they're usually for bugs/feature requests, etc.

[gucio321]

Another proposal: let's enable "Discussions" in this repo and move topics like these there instead of making many "issues" as they're usually for bugs/feature requests, etc.

it is done now. Converting this to discussion

[AllenDang]

@gucio321 I just created the branch protection rules

[gucio321]

asesome!

[gucio321]

Hi!
according to #105 we need to extend our test workflow to windows, since (like we saw) the code may compile on ubuntu, but may crash on windows