This repository was archived by the owner on Aug 24, 2023. It is now read-only.
Update to skeleton-aws-lambda, Pare CODEOWNERS, and Add Lineage Configuration #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🗣 Description
This updates this project to align with cisagov/skeleton-aws-lambda, reduces the
CODEOWNERS
file to the primary contributors, and adds a Lineage configuration to ease future maintainability.This project was started before I created cisagov/skeleton-aws-lambda, so it was based on cisagov/skeleton-python-library. In order to support Lineage correctly I needed to pull from cisagov/skeleton-aws-lambda to, hopefully, readily merge future Lineage PRs.
💭 Motivation and Context
Having repositories tie in to the newer Lineage process is good for maintainability.
CODEOWNERS
should reflect "true" owners.🧪 Testing
Automated testing.
📷 Screenshots (if appropriate)
🚥 Types of Changes
✅ Checklist