-
Notifications
You must be signed in to change notification settings - Fork 4
feat: Added function New-PipelineRun #61
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.
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
Open
Lucas-c-B
wants to merge
10
commits into
main
Choose a base branch
from
feature-new-run
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix: Add support for files beginning with a dot
Added a new function called New-PipelineRun, which can start a pipelin run in an Azure DevOps Project programmatically docs: Added comment based help to New-PipelineRun Added comment based help to New-PipelineRun fix: Add missing ValidateScript Add missing ValidateScript fix: should process input fix: param validator collectionUri fix: fixed service connection parameter set feat: Add function Get-PipelineRun Add function Get-PipelineRun that gets all or specific runs from the specified pipeline fix: formatting formatting feat: added classification nodes endpoint feat: Add PipelineFolderPath parameter to be able to place a pipeline in a folder in azure devops to the module: New-AzDoPipeline Add PipelineFolderPath parameter to be able to place a pipeline in a folder in azure devops to the module: New-AzDoPipeline feat: add public cmdlet to create pull requests individually or in bulk (supports pipeline) fix: 💩 Fixing breaking change for Get-AzAccessToken Fixing Get-AzAccessToken, but this needs the Invoke-RestMethod function needs refactoring feat: add support for content type header fix: Add support for files beginning with a dot refactor: Enhance Get-PipelineRun function to use splatting and return structured output refactor: Improve New-PipelineRun function output structure
a3e5a72
to
ddb4ff0
Compare
This reverts commit b7f5b02.
baswijdenes
approved these changes
Feb 28, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the naming convention to "AzDo" and I will approve the PR.
auto-merge was automatically disabled
February 28, 2025 10:31
Squash merges are not allowed on this repository
@Manbearpiet Want me to merge the PR or wait for the user to merge? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added a new function called New-PipelineRun, which can start a pipeline run in an Azure DevOps Project programmatically
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: