MeltanoLabs / MeltanoLabs/Meta
Common CI Workflows for MeltanoLabs taps and targets
Open
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
All taps and targets in MeltanoLabs can use a common set of workflow files for:
- Create/update release drafts.
- Publish to PyPi when GitHub release is published. (Use dynamic versioning.)
- Check semantic PR title rules.
Repos that don't have custom service requirements (such as needing to pre-launch a Postgres instance) can also use common workflows for:
- Standard CI tests.
Initial proof of concept PR:
- #33
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with proof-of-concept PR #33 and compare its workflow files with the release, PyPI, semantic PR title, and standard CI requirements listed here. Done means common workflows cover applicable MeltanoLabs taps and targets, while repositories with custom service requirements are excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100