Clone boilerplate using a tag about create-graphql

[lucasbento]

Fixed on #109, thank you for the great help, @shimulch.

[felippepuhle]

I guess the last commit from master is a good start. We could define this later, great job!

[shimulch]

Hi, Is this issue open? Can I have a try?
Also how a tag should be selected to be cloned?

[felippepuhle]

Go ahead @shimulch

[lucasbento]

@shimulch: hey, of course!

We should define a specific tag or commit hash in the generator to clone the repo, that variable should be easy to change since we can keep increasing it based on the boilerplate commits/releases.

I think a commit hash is easier for now since it doesn't require any changes in the boilerplate code.

I can't point the file to change it right now because I'm on cellphone but it should be in the generator-graphql init command.

@felippepuhle: can you specify which commit hash is the best to clone the boilerplate at the moment? I think it should be one before the changes to the loaders.

[JCMais]

Clone happens here https://github.com/graphql-community/create-graphql/blob/fbb25fa3adc7e8014bcfbb88220b708ff5fc1464/packages/generator/src/app/index.js#L42

[shimulch]

@lucasbento Thanks for clarifications.
Here you can see my work so far.

master...shimulch:feature/clone_boilerplate_using_a_tag

It can now checkout to a specific commit hash after cloning the boilerplate. Now how you suggest to have a controllable variable for this task?

[lucasbento]

@shimulch: nice work!

I think you can keep it at the top as constant along with repository so it can be easily changed.

@sibelius, @felippepuhle, @JCMais: can any of you tell me a commit hash to use?

[shimulch]

I kept the last commit from master branch as commit hash. And its on a const to be changed.

[shimulch]

@felippepuhle I have already put the last has from master in the PR. :-)

[shimulch]

#109

[felippepuhle]

Yeah, I saw that @shimulch, thanks!