Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

share this project on official gitlab templates #8

Closed
4383 opened this issue Sep 26, 2017 · 6 comments
Closed

share this project on official gitlab templates #8

4383 opened this issue Sep 26, 2017 · 6 comments

Comments

@4383
Copy link
Collaborator

4383 commented Sep 26, 2017

We can generate explore gitlab official template for try to generate a version of cookiecutter-pypkg compatible with these templates.

CI/CD can help you to generate this custome version without cookiecutter.
In other words we can use CI/CD/cookiecutter for generate a standalone version compatible with gitlab ecosystem and share this on the official gitlab repository. After that all gitlab users can choose our cookiecutter-pypkg directly in gitlab interface.
https://docs.gitlab.com/ee/gitlab-basics/create-project.html

@4383
Copy link
Collaborator Author

4383 commented Sep 26, 2017

we need to inspect how this official templates are makes

@AntoineCezar
Copy link
Owner

I like the idea, however it seems to be static files.

@4383
Copy link
Collaborator Author

4383 commented Sep 27, 2017

I don't know how to work gitlab template but I think it's static files. With CI we can easily automatizing static file generation from this template

@4383
Copy link
Collaborator Author

4383 commented Sep 27, 2017

@ewjoachim do you have any ideas/suggestions about this?

@ewjoachim
Copy link

Not really, I haven't had the opportunity to work with GitLab since it introduced templates. But yes, it can be nice to only do the work once.

As a side note, as much as I like bootstrapping tools, I prefer having the opportunity to review every file before it's commited on the repo, so that I don't get too much boilerplate cargo cult files. My ideal template would include some doc explaining all the "specific files" of the project, and how they work, for both the person using cookiecutter/..., and the future devs of the repo. The advantage of cookie cutter in this case is that one may get rid of useless file from the beginning.

@AntoineCezar
Copy link
Owner

I think gitlab integration is not feasable. If someone want gitlab template it can generate a static one from the cookiecutter one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants