@alan-ssvlabs
Also change description so it will automatically close the issue (use "close" or "fix")
See: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

Thanks @GalRogozinski, updated the description and made the suggested changes

But for the file permissions it fails the gosec because gosec suggests 600 or less, and it raises permission denied for the json files when using git add .

@alan-ssvlabs
So maybe do 644?
Basically I want everyone to be able to read... If owner can write I guess it is ok

@alan-ssvlabs So maybe do 644? Basically I want everyone to be able to read... If owner can write I guess it is ok

Did it as 644, gosec is not happy because it expect 600 or less so I added nosec. Also the permission denied messages are still there on git add...

@alan-ssvlabs
not sure why with 0644 you are getting those

Very strangely I didn't get any permission errors before editing this 444 or 644 permissions, now no matter how I set it I get permission errors for both go generate and git add. I suspect it is my local problem, can you clone this branch and try to generate and git add? @GalRogozinski

@alan-ssvlabs
I am currently getting:

types/spectest/generate/tests/committeemember.CommitteeMemberTest_committee_member_has_quorum_3f1.json: Permission denied
types/spectest/generate/tests/committeemember.CommitteeMemberTest_committee_member_no_quorum_duplicate.json: Permission denied
types/spectest/generate/tests/committeemember.CommitteeMemberTest_committee_member_quorum_with_duplicate.json: Permission denied
types/spectest/generate/tests/consensusdataproposer.ProposerSpecTest_consensus_data_versioned_blinded_block_corrupted_consensus_data.json: Permission denied
types/spectest/generate/tests/consensusdataproposer.ProposerSpecTest_consensus_data_versioned_blinded_block_unknown_version.json: Permission denied
types/spectest/generate/tests/consensusdataproposer.ProposerSpecTest_consensus_data_versioned_blinded_block_validation.json: Permission denied

I think what is happening is once the files were created once w.o write permission it is hard for them to be deleted.
So locally do a chmod on all of them
and only use 0x644

Seems I gotten myself to a position where I get permission errors always unless if I use the SUDO flag
and no sudo chmod helps even if permission changes
Had to delete everything to make it work...

maybe we go back to original permissions if this causes issues.
It isn't the biggest deal... It was supposed to be easy