Skip to content

Add PR trigger to pipeline #251

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
florelis merged 5 commits into from
Aug 10, 2024
Merged

Add PR trigger to pipeline #251

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7e23670
Add PR trigger
florelis Aug 8, 2024
1d569be
Wrong branch name...
florelis Aug 8, 2024
762cb23
add paths
florelis Aug 9, 2024
7ef9582
Remove tag, paths
florelis Aug 9, 2024
4a65191
skip tagging
florelis Aug 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions pipelines/winget-cli-restsource-ci-pr.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,11 @@
# Copyright (c) Microsoft Corporation. All rights reserved
# CI pipeline for winget-cli-restsource

# TODO: The forked pr builds need to have the same permission as non-forked ones to access
# project's internal nuget feed. Remove DisablePipelineConfigDetector variable when
# a long term fix is available.
variables:
- name: DisablePipelineConfigDetector
value: true
# PR triggers
pr:
branches:
include:
- main

resources:
repositories:
Expand All @@ -22,9 +21,10 @@ extends:
name: Azure-Pipelines-1ESPT-ExDShared
image: windows-2022
os: windows
customBuildTags:
# This is added by 1ES migration tool and it is okay to remove in the future.
- ES365AIMigrationTooling

settings:
# Builds from forked repos do not have permissions to set tags
skipBuildTagsForGitHubPullRequests: true

stages:
- stage: Build_Publish_Test
Expand Down