`python - conda` should have limited `CI` triggers

Open Beginner friendly
#46,697 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
azure, python

Research direction

Start by locating the python - conda build definition and reviewing its current trigger configuration. Compare it with the two linked Azure DevOps builds to identify pushes that should not have triggered it. Done means branch and path filters are configured so unrelated pushes no longer start this CI build.

Written by the indexing model from the issue text.

Description

It's triggering on pushes, because we have no branch or path filters on the build definition. Let's add those.

Dominant language
Python
Stars
5.6k
Forks
3.4k
Avg merge
1d 22h
Merged PRs (30d)
199

Contributor guide

Open the contributing guide

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.