Setting up CI (#3)
* infra: boilerplate CI * ci: workflow name * chore: typo * docs: badges * docs: status badge
This commit is contained in:
parent
a0a2db7c32
commit
276b9e339c
2 changed files with 27 additions and 0 deletions
25
.github/workflows/pythonpackage.yml
vendored
Normal file
25
.github/workflows/pythonpackage.yml
vendored
Normal file
|
@ -0,0 +1,25 @@
|
|||
name: CarbonCopy CICD
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
max-parallel: 4
|
||||
matrix:
|
||||
python-version: [3.6, 3.7]
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v1
|
||||
- name: Set up Python ${{ matrix.python-version }}
|
||||
uses: actions/setup-python@v1
|
||||
with:
|
||||
python-version: ${{ matrix.python-version }}
|
||||
- name: Install dependencies
|
||||
run: |
|
||||
python -m pip install --upgrade pip
|
||||
pip install -r requirements.txt
|
||||
- name: Formatter
|
||||
run: |
|
||||
black src *.py --check
|
|
@ -2,6 +2,8 @@
|
|||
|
||||
Keep your repositories up-to-date with their templates in a few keystrokes.
|
||||
|
||||
![CarbonCopy CICD](https://github.com/mcataford/carboncopy/workflows/CarbonCopy%20CICD/badge.svg) ![PyPi version](https://img.shields.io/pypi/v/carboncopy) ![Wheel](https://img.shields.io/pypi/wheel/carboncopy) ![License](https://img.shields.io/pypi/l/carboncopy) ![Status](https://img.shields.io/pypi/status/carboncopy)
|
||||
|
||||
## ❓ Why `carboncopy`?
|
||||
|
||||
[Github Template Repositories](https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/) made it really easy to skip project boilerplate setup steps and to produce "new project kits" that ensure that all your (or your organization's) new projects have all the must-haves. Problem is, templates aren't set in stone and it's likely that templates get updated after some projects have been spawned from it.
|
||||
|
|
Reference in a new issue