-
Notifications
You must be signed in to change notification settings - Fork 80
Issues: Azure/pipelines
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Bug] Could not queue the build because there were validation errors or warnings.
need-to-triage
Requires investigation
#95
opened Apr 15, 2024 by
priscofarina
[Bug] Node.js 16 is deprecated and should be replace with Node.js 20
need-to-triage
Requires investigation
#94
opened Feb 6, 2024 by
G-Moore2
[Bug] Fix broken integration tests
need-to-triage
Requires investigation
#89
opened Aug 23, 2023 by
tjcorr
[Bug] - Cross REPO connection is not happening
need-to-triage
Requires investigation
#84
opened Jul 6, 2023 by
saivamsibodavulaTR
[Question] Is it possible to specify the Azure branch to trigger the pipeline on
need-to-triage
Requires investigation
#80
opened Apr 11, 2023 by
deppsu
[Bug] Sample in README needs updating
need-to-triage
Requires investigation
#68
opened Jul 28, 2022 by
keifgwinn
[Question/Feature-Request] Pass template parameters for deployment at approval
need-to-triage
Requires investigation
#62
opened May 17, 2022 by
davsucks
[Documentation-Request] Specify Scopes Required for PAT
need-to-triage
Requires investigation
#61
opened May 16, 2022 by
nibanks
[Bug/Question/Feature-Request] Parameters passed to Pipeline are not being accepted
need-to-triage
Requires investigation
#60
opened May 6, 2022 by
oscarare
[Question] How to select stages to run?
need-to-triage
Requires investigation
#57
opened Mar 8, 2022 by
parikshit14
[Bug] expected - waiting for status to be reported
need-to-triage
Requires investigation
#54
opened Feb 15, 2022 by
markbrassingtonct
PipelineName does not perform an exact search - results in errors if pipelines contain the same name
bug
Something isn't working
P1
Some scenario broken but workaround exists
#33
opened Jun 2, 2021 by
JamesBurnside
Using an enterprise http/https proxy for this action
enhancement
New feature or request
idle
Inactive for 14 days
question
Further information is requested
#30
opened May 19, 2021 by
dos1701
Multiple pipelines with the same name
enhancement
New feature or request
#28
opened Apr 21, 2021 by
mbpolan
Error running pipeline from action
question
Further information is requested
#16
opened May 18, 2020 by
searledan
Any examples to consume the artifacts from a workflow?
question
Further information is requested
#15
opened Feb 20, 2020 by
seanyen
How to link Azure DevOps pipeline with GitHub repo
enhancement
New feature or request
idle
Inactive for 14 days
#13
opened Feb 7, 2020 by
eric-labelle
ProTip!
no:milestone will show everything without a milestone.