You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create an organization. Mine is my username, but you can probably think of something cooler.
Create a new public project associated with the organization. I took the easy route and named mine 'pynndescent', but you can have multiple repos associated with a project (e.g. UMAP could go under here too eventually), so something more generic might be more appropriate.
On the left set of icons, click on 'Pipeline'. In the pane that appears click the 'New' button, then 'New build pipeline'. Select github from the list of providers and then this repo (obviously).
If you haven't already been prompted to, you will be told that you need to install the Azure Pipelines GitHub App for this repo. This provides the typical read/write permissions.
The existing azure-pipelines.yml file in this repo will be picked up. Once permissions from the previous step have been granted, you can click the 'Run' button on the top right to kick it off.
That should be it. You can see the history of the builds if the current pipeline is selected on the main pipeline page. Also on the very top right is the context menu (the easy-to-miss three vertical dots under which everything useful is hidden according to the diktats of modern UI design). In there, under 'Status badge' is the URL for the all-important README badge.
The text was updated successfully, but these errors were encountered:
I have probably forgotten some steps, but this is mostly all you need to know:
azure-pipelines.yml
file in this repo will be picked up. Once permissions from the previous step have been granted, you can click the 'Run' button on the top right to kick it off.The text was updated successfully, but these errors were encountered: