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

Checking to see if this impacts check-enforcer #18375

Closed
wants to merge 1 commit into from
Closed

Checking to see if this impacts check-enforcer #18375

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 0 additions & 38 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop

This file was deleted.

15 changes: 4 additions & 11 deletions eng/CHECKENFORCER
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,11 +41,9 @@ message: >

# What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them.
In order to bootstrap pipelines for a new service, please perform following steps:

## For data-plane/track 2 SDKs
Issue the following command as a pull request comment:
Often, new services do not have validation pipelines associated with them,
in order to bootstrap pipelines for a new service, you can issue the following
command as a pull request comment:

```
/azp run prepare-pipelines
Expand All @@ -57,9 +55,4 @@ message: >

```
/azp run net - [service] - ci
```

## For track 1 management-plane SDKs

Please open a separate PR and to your service SDK path in [this file](https://github.com/Azure/azure-sdk-for-net/blob/master/eng/pipelines/mgmt.yml). Once that PR has been merged, you can re-run the pipeline to trigger the verification.

```