microsoft / microsoft/cmd-call-graph
Automate pushing releases to PyPI
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 59
- Forks
- 23
- Avg merge
- 16h 39m
- Merged PRs (30d)
- 1
Description
Documentation: https://docs.microsoft.com/en-us/azure/devops/pipelines/artifacts/pypi?view=vsts&tabs=yaml
- define what triggers publishing to PyPI
- define how to handle version numbers
- define how to handle the changelog
- handle authentication (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/twine-authenticate?view=vsts)
- implement pushing to PyPI
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 the linked Azure Pipelines PyPI documentation and the Twine authentication documentation. Define the publishing trigger, version-number and changelog handling, and authentication approach before implementing the release workflow. Done means releases are pushed to PyPI through the documented process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100