Switch from Travis to GitHub Actions for CI

.github/workflows/ci.yaml

@@ -0,0 +1,38 @@
+name: CI
+on:
+  pull_request:
+  push:
+    branches:
+      - master
+
+# The goal here is to cancel older workflows when a PR is updated (because it's pointless work)
+concurrency:
+  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+  cancel-in-progress: true
+
+jobs:
+  generate:
+    name: generate
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt
+
+      - name: Test generation
+        run: |
+          echo "from Default.settings import *" > settings.py
+          ./generate.py

.gitignore

@@ -1,6 +1,7 @@
 *.pyc
 __pycache__
 env
+/.idea/
 
 # ignore mappings and settings files
 /mappings.py

README.md

@@ -1,7 +1,5 @@
 Python FHIR Parser
 ==================
-[![Build Status](https://travis-ci.org/palfrey/fhir-parser.svg?branch=master)](https://travis-ci.org/palfrey/fhir-parser)
-
 A Python FHIR specification parser for model class generation.
 If you've come here because you want _Swift_ or _Python_ classes for FHIR data models, look at our client libraries instead:
 
@@ -24,7 +22,7 @@ These representations are then used by [Jinja][] templates to create classes in
 This script does its job for the most part, but it doesn't yet handle all FHIR peculiarities and there's no guarantee the output is correct or complete.
 This repository **does not include the templates and base classes** needed for class generation, you must do this yourself in your project.
 You will typically add this repo as a submodule to your framework project, create a directory that contains the necessary base classes and templates, create _settings_ and _mappings_ files and run the script.
-Examples on what you would need to do for Python classes can be found in _Sample/settings.py_, _Sample/mappings.py_ and _Sample/templates*_.
+Examples on what you would need to do for Python classes can be found in _Default/settings.py_, _Default/mappings.py_ and _Sample/templates*_.
 
 
 Use

requirements.txt

@@ -1,4 +1,3 @@
-Jinja2>=3.0
-MarkupSafe==0.23
+colorlog>=2.10.0
+jinja2>=3.0
 requests>=2.13.0
-colorlog==2.10.0