Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Teams Chatbot]: Clarify Python dev-feed publication from a branch versus PyPI release

Open Beginner friendly
  • Is something wrong?
#49,548 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
documentation, release

Research direction

Start with doc/dev/release.md in Azure/azure-sdk-for-python, which covers PyPI release guidance, and read doc/eng_sys_checks.md for the dev-feed build semantics. The issue asks for a new dev-feed subsection in the release doc that says to queue the service pipeline on the branch with the changes, set SetDevVersion=true, run Build and Integration only, and skip Release. Done means that subsection exists and matches the behavior described in eng_sys_checks.md.

Written by the indexing model from the issue text.

Description

customer-reported question
Description

A user asked how to distribute a private-preview Python SDK build through the Azure Artifacts dev/public ADO feed and which branch to use. The bot incorrectly steered them toward undocumented private-feed guidance and failed to explain the actual Python dev-feed flow from the branch containing the changes.

Conversation

https://teams.microsoft.com/l/message/19%3Ab97d98e6d22c41e0970a1150b484d935%40thread.skype/1791943733577?groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&createdTime=1791943733577&parentMessageId=1791943733577

Root cause

The KB had PyPI release guidance in doc/dev/release.md and dev-feed build semantics in doc/eng_sys_checks.md, but it lacked one discoverable instruction that dev-feed publication should be queued from the branch containing the changes with SetDevVersion=true and Build + Integration only.

Fixed document
  • KB document: azure_sdk_for_python_docs/dev#release.md
  • Upstream: Azure/azure-sdk-for-python, main:/doc/dev/release.md
  • Source: https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/release.md
  • Validated change: Added a dev-feed subsection to the Python release doc that tells users to queue the same service pipeline on the branch with their changes, set SetDevVersion=true, publish during Integration, and skip the Release stage because PyPI release stages are gated off for dev builds.
Validation

Result: Passed — the candidate answer told the user to use the branch containing the changes, set SetDevVersion=true, run Build and Integration, skip Release, and distinguished Azure Artifacts dev-feed publication from the normal PyPI release flow.
Trace ID: 56c6dda8c820acf7612a99c72dc85b96

Expected behavior

When asked about publishing a Python SDK to the Azure Artifacts dev/public ADO feed, the bot should explain that this is not the normal PyPI release path, identify that the service pipeline can be queued on the branch containing the changes, and state the material requirements: SetDevVersion=true, Build + Integration, and no Release stage. It should avoid redirecting the user to private-preview private-feed guidance when the question is specifically about the Python dev feed.

Dominant language
Python
Stars
5.6k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
218

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/azure-sdk-for-python

All issues in Azure/azure-sdk-for-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.