Ah, well, if that's all: https://github.com/solcloud/Counter-Strike/pull/28

(It's kinda weird, because to make a PR, I had to make a fork, and then I added the licence to my fork, even though I'm not allowed to pick the licence, but )

It makes me want to start several PRs with conflicting licenses.

bring it :D now I thinks about suing anybody forking repo with licence change :D no seriously it is merged now so world is safe again :)

They went with a more open license. Try to do better next time with your license choices. GNU is not nearly as open as the "DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE."

https://github.com/solcloud/Counter-Strike/pull/27/files

Glad they did, because now my fork illegally adding a licence is legal again. Phew!

this is awesome :D

Just FWI, it's not illegal to add an incorrect license to a repository you don't have the rights to. It's simply a lie. The copyright notice is just a statement from the author, it doesn't per se define the terms under which the project is distributed. What defines them is the fact that it's the author who put the file there.

Heh, fair enough I suppose, though it's definitely not very nice to make people believe that I can give them permission to do things, when I don't.

What license do you want to share your work under? MIT? GPL? There's a couple of trade-offs in that choice.

Github has an overview of some of your options: https://github.com/readme/guides/open-source-licensing