mindsdb / mindsdb/mindsdb_python_sdk
Update docs after release published
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 16
- Avg merge
- 6h 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
At the moment to update sdk docs you have to update 'docs' branch
Describe the solution you'd like
It would be better if it was done during publishing 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
No file or release workflow is named. Start by reviewing how the sdk docs branch is currently updated and how releases are published; done means publishing a release also updates the sdk docs without a separate manual docs-branch update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100