Skip to content

[DO NOT MERGE] Testing LintDiff behavior on duplicate "input-file" definition in tag #34215

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

danieljurek
Copy link
Member

@danieljurek danieljurek commented Apr 24, 2025

First change: ran against the whole readme.md file itself, no tag https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4795947&view=logs&j=0574a2a6-2d0a-5ec6-40e4-4c6e2f70bea2&t=80c3e782-49f0-5d1c-70dd-cbee57bdd0c7 (the default tag?)

Second change: Ran against the specific tag... it's as if the later definition overrides https://github.com/Azure/azure-rest-api-specs/pull/34215/checks?check_run_id=41108302900

Copy link

openapi-pipeline-app bot commented Apr 24, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ The required check named Swagger ModelValidation has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

Copy link

openapi-pipeline-app bot commented Apr 24, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@danieljurek danieljurek changed the title Change 1: Alter first instance of tag [DO NOT MERGE] Testing LintDiff behavior on duplicate "input-file" definition in tag Apr 24, 2025
@github-actions github-actions bot added the brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. label Apr 24, 2025
Copy link

github-actions bot commented Apr 24, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Microsoft.Aadiam
Python azure-mgmt-azureactivedirectory
Java com.azure.resourcemanager:azure-resourcemanager-azureactivedirectory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment