Skip to content
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

Jump to bottom

SDK azure-sdk-for-net-track2 check failing due to existing code. #3877

Closed
pansharm-ms opened this issue Aug 8, 2022 · 2 comments
Closed

SDK azure-sdk-for-net-track2 check failing due to existing code. #3877

pansharm-ms opened this issue Aug 8, 2022 · 2 comments
Assignees
@pansharm-ms
Labels
Spec PR Tools Tooling that runs in azure-rest-api-specs repo.

Comments

@pansharm-ms
Copy link

I have created a PR in the azure api specs repository: 20142
One check is failing in this PR: SDK azure-sdk-for-net-track2
This check is not related to the code changed in PR but is failing due to existing code in repository.
Can you please resolve this issue.
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 8, 2022
@kurtzeborn kurtzeborn added Spec PR Tools Tooling that runs in azure-rest-api-specs repo. and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Oct 31, 2022
@raych1
Copy link
Member

raych1 commented Nov 1, 2022

@pansharm-ms , please resolve the branch conflicts then re-run the check with /azp run.

@raych1
Copy link
Member

raych1 commented Nov 29, 2022

I close this issue as there's no response. Feel free to re-open it.

@raych1 raych1 closed this as completed Nov 29, 2022
@raych1 raych1 moved this to Done in Spec PR Tools Nov 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pansharm-ms pansharm-ms

Labels
Spec PR Tools Tooling that runs in azure-rest-api-specs repo.
Projects
Spec PR Tools
Status: 🎊 Closed
Milestone
No milestone
Development

No branches or pull requests
3 participants
@raych1 @kurtzeborn @pansharm-ms