Add QCI simulator (Partner PR - Do Not Close) #608
Conversation
|
Microsoft authors of articles need to make updates through the private repository, so the updates can be staged and validated by current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged. It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows: Public repo URL: We have closed this pull request. Please resubmit the updates through the private repo. For more information, see the contributor guide. |
Bradben
changed the title
|
Learn Build status updates of commit c733c04:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/machines/backend-simulators.md | Details | ||
| articles/hybrid-computing-integrated.md | ✅Succeeded | ||
| articles/quantum-computing-target-profiles.md | ✅Succeeded |
articles/machines/backend-simulators.md
- Line 5, Column 10: [Warning: ms-date-invalid - See documentation]
Invalid date format for 'ms.date': '067/01/2023'. Must be a date in format M/D/YYYY, no more than 30 days from today.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
|
Learn Build status updates of commit c2dcc28: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
#label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Learn Build status updates of commit 74f4d93: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 4824558: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Thanks, @qci-amos - looks good to me. |
|
Learn Build status updates of commit b857820: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit f39e653: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. For any questions, please:
|
|
Learn Build status updates of commit 601f487: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit d05f33e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
For this: Under Could we make this a single comparative table for all targets. It will make it easier for people to compare features between targets. For this:
|
|
Learn Build status updates of commit 11bea31: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit 200a525: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit a50493c: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
No description provided.