fixed double linked list and create test for it #272 and fixed contributing.md

[Miraddo]

• As we know in the double-linked list, we should have the Next and the Prevent address in each node. In the Test AddAtBeg, I wasn't able to switch between next and prev so, I fixed that part, and now I guess everything Is fine.

For more clear staff, look at this example :

It was like :
first : &{1 nil nil}
second : &{2 address nil}
third : &{3 address nil}

and now it looks like this:

first : &{1 nil address}
second : &{2 address address}
third : &{3 address nil}

• I updated pull request file inside .github folder
• I updated contributing.md based on Cpp Contributing File
• I changed all files and folders names based on contributing guidelines

[lgtm-com]

This pull request introduces 1 alert and fixes 1 when merging 3eb77fe into 0a282fa - view on LGTM.com

new alerts:

• 1 for Use of insufficient randomness as the key of a cryptographic algorithm

fixed alerts:

• 1 for Use of insufficient randomness as the key of a cryptographic algorithm

[lgtm-com]

This pull request introduces 1 alert and fixes 1 when merging 48e0ccb into 0a282fa - view on LGTM.com

new alerts:

• 1 for Use of insufficient randomness as the key of a cryptographic algorithm

fixed alerts:

• 1 for Use of insufficient randomness as the key of a cryptographic algorithm

[cclauss]

Files changed 109 seems a bit high. Can you please visit https://github.com/Miraddo/Go and click on Fetch upstream (that should be just below the green Code button). Thanks.

[Miraddo]

Files changed 109 seems a bit high. Can you please visit https://github.com/Miraddo/Go and click on Fetch upstream (that should be just below the green Code button). Thanks.

@cclauss , thank you for your reviewing, It seems that part is disable for me "This branch is not behind the upstream"

[cclauss]

Did you really modify 109 files?

[Miraddo]

Did you really modify 109 files?

Yes, because we didn't have a "Contribute Guideline," and every developer put their own style on the file's name. Some people created files with PascalCase, camelCase, or they're just put names without any standard.

So to have more clear and readable file names, after fixed contributing guidelines markdown file, I decided to fix them as snake_case style for both files and folders.

I didn't change codes except for one line in the genetic algorithm file. golangci-lint shows an error, so I found the problem, and you can see my last commit. I fixed it.

For sure, I should mention package names changed too.

[siriak]

LGTM, thanks!