😬 bad merge on my side 🤦

Need review of this and test cc @CiaranEvans

How would you like me to test it @vincentsarago?

Is this repo meant to be a template that you can choose when making a new repo on Github or do you check it out and rename stuff?

Only way I could test it at the mo is create my own repo and chuck this in? I think?

Is this repo meant to be a template that you can choose when making a new repo on Github or do you check it out and rename stuff?

It's a CLI that create brand new project with the correct name

# Create a project
$ pyseed create awesomepythonproject

# List files created
$ ls -1 awesomepythonproject
.pre-commit-config.yaml
README.md
awesomepythonproject/
requirements-dev.txt
requirements.txt
setup.py
tests/
tox.ini

This PR adds an option for adding a CI config (either github or circleci). This is the first time I write github action so I'm not sure what I'm doing ;-)

Let me try it on this repo directly anyway

Ah okay, how do I install it for use?

for now you have to clone the repo but it should be one pypi later today.

Cool thanks :D

Seems like it's all pretty sensible at the mo, I'll use it in a dummy repo and see!

Though this will publish for every push to any branch right now (I think)

Though this will publish for every push to any branch right now (I think)

publish should only run on tags if: contains(github.ref, 'tags') and if tag == python version

      - name: Check git tag vs. version
        # We Only deploy to PyPi if github tag match the python version
        run: |
            VERSION=$(python setup.py --version)
            if [ "$VERSION" = "$RELEASE_VERSION" ]; then exit 0; else exit 3; fi

I'm trying it for this repo over #12