We currently launch the PTVS pipeline as part of the pylance release process (at the end) to make sure PTVS ingests the latest pylance and inserts it into VS. The problem is that this is done with a PAT, which is stored as a secret in the pylance release github action.
Bill is moving pylance release to azdo. Once that's done, we can launch the PTVS build via a pipeline trigger without the need for the PAT and we can remove the secret and the PAT.
@bschnurr - Please let me know when the pylance release has been moved to azdo and is working, and I can work on the PTVS pipeline chaining. :)
We currently launch the PTVS pipeline as part of the pylance release process (at the end) to make sure PTVS ingests the latest pylance and inserts it into VS. The problem is that this is done with a PAT, which is stored as a secret in the pylance release github action.
Bill is moving pylance release to azdo. Once that's done, we can launch the PTVS build via a pipeline trigger without the need for the PAT and we can remove the secret and the PAT.
@bschnurr - Please let me know when the pylance release has been moved to azdo and is working, and I can work on the PTVS pipeline chaining. :)