Unstructured-IO / Unstructured-IO/unstructured-api
feat/create a github action to publish new unstructured-api releases
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 951
- Forks
- 192
- Avg merge
- 7d 8h
- Merged PRs (30d)
- 2
Description
When the changelog drops a -dev in the first entry, we should automatically create a github release to avoid those becoming stale.
Definition of done
- A github action listens for merges to main
- If the changelog starts with a release version, grab the notes and create a github release
Contributor guide
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
Locate the changelog and workflow configuration, then read the changelog's first entry and check how merges to main trigger automation. Done means a GitHub Action detects a release version instead of -dev, extracts the notes, and creates a GitHub release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100