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.

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

Fix to allow users to specify a location for a project to run in Azure Quantum #3632

Merged
merged 1 commit into from
Jul 13, 2021

Conversation

ricardo-espinoza
Copy link
Contributor

Because of a syntax difference between commands dotnet build and dotnet run, one of them expects the project location to be specified as a positional parameter and another as a named parameter. Because of this, we had a bug in which the user could not specify the location of a project outside of the current folder.


This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

  • Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
  • Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Copy link

@swernli swernli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank for fixing!

@yonzhan
Copy link
Collaborator

yonzhan commented Jul 13, 2021

Quantum

@kairu-ms kairu-ms merged commit f89aa6d into Azure:main Jul 13, 2021
@ricardo-espinoza ricardo-espinoza added the Quantum az quantum label Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Quantum az quantum
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants