microsoft / microsoft/azure-devops-go-api
Add pipeline configuration details in pipeline client
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 223
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
While using pipeline client, I noticed that configuration returns just Type and the rest is dropped (?). API, based on pipeline type (i.e. yaml or designerJson), returns additional fields:
yaml:
"configuration": {
"path": "azure-pipelines.yml",
"repository": {
"id": "eb96368e-87df-4744-9448-023a1ae6eb53",
"type": "azureReposGit"
},
"type": "yaml"
},
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in azuredevops/v7/pipelines/models.go at the pipeline configuration model linked in the issue, then inspect how the pipeline client decodes the API response. Ensure YAML configuration retains the path and repository data shown in the example, while preserving the type field. Done means those fields are available to callers instead of being dropped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- api, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100