Setting up CI

[lemonsaurus]

We'll need CI for this project to do two things:

• Lint the project and ensure it meets our qualitative standards
• Deploy the project to PyPI whenever we push to master.

We'll probably want to use Azure Pipelines for this, since we've already got that set up for other repos.

[lemonsaurus]

This should be our number one priority for this repo - it's in fairly usable state right now, but far from done. We should be publishing it to PyPI so we can use it for our projects, and then we can work on it as we see needs arise.

[gdude2002]

It would probably make your life easier if you cloned the Azure release pipeline for django-simple-bulma and updated it. Off the top of my head:

• Cloned pipelines do not copy secret variables, so you'll need to update the pypi login vars
• Go through the CI YAML file and copy over the artifact deployment steps if they aren't already in the YAML for this repo - remember to update the paths as appropriate, if needed
• Copy over all of the scripts from the other repo and edit the github release one to make sure it's pointing at the correct repo - sorry, I hardcoded this, didn't get around to making it use env vars
• Go through both release stages in the pipeline, look at their tasks, and update them to match the above

That should get you working releases.

[lemonsaurus]

thanks @gdude2002, that was going to be my approach and I appreciate the tips.

[lemonsaurus]

Okay, this is now working.