[Bug]: Broken links across the repository #2000
Assignees
Labels
documentation
Improvements or additions to documentation
Comments
|
I did not know about this package, and I love it! Thank you for the heads up! Re-reviewing your PR -- it looks like the ones you addressed were handled? FYI, some of the links we post are internal-only, which I understand can be frustrating and counter-intuitive in an open-source repo. Those links will very likely remain in our readme's. |
corinagum
added
documentation
This was referenced Sep 25, 2024
corinagum
pushed a commit
that referenced
this issue
Sep 25, 2024
## Linked issues closes: #minor ## Details Provide a list of your changes here. If you are fixing a bug, please provide steps to reproduce the bug. Reference: #2000 #### Change details > Describe your changes, with screenshots and code snippets as appropriate Link to Azure OpenAI On Your Data is corrected ## Attestation Checklist - [x] My code follows the style guidelines of this project - I have checked for/fixed spelling, linting, and other errors - I have commented my code for clarity - I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient) - My changes generate no new warnings - I have added tests that validates my changes, and provides sufficient test coverage. I have tested with: - Local testing - E2E testing in Teams - New and existing unit tests pass locally with my changes ### Additional information > Feel free to add other relevant information below
corinagum
added a commit
that referenced
this issue
Sep 25, 2024
## Linked issues closes: #minor ## Details Provide a list of your changes here. If you are fixing a bug, please provide steps to reproduce the bug. Reference: #2000 #### Change details > Describe your changes, with screenshots and code snippets as appropriate Link to "other-ways-to-run-the-sample" is corrected ## Attestation Checklist - [ ] My code follows the style guidelines of this project - I have checked for/fixed spelling, linting, and other errors - I have commented my code for clarity - I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient) - My changes generate no new warnings - I have added tests that validates my changes, and provides sufficient test coverage. I have tested with: - Local testing - E2E testing in Teams - New and existing unit tests pass locally with my changes ### Additional information > Feel free to add other relevant information below --------- Co-authored-by: Corina <14900841+corinagum@users.noreply.github.com>
corinagum
added a commit
that referenced
this issue
Sep 25, 2024
## Linked issues closes: #minor ## Details Provide a list of your changes here. If you are fixing a bug, please provide steps to reproduce the bug. Reference: #2000 #### Change details > Describe your changes, with screenshots and code snippets as appropriate Link to "other-ways-to-run-the-sample" is corrected ## Attestation Checklist - [ ] My code follows the style guidelines of this project - I have checked for/fixed spelling, linting, and other errors - I have commented my code for clarity - I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient) - My changes generate no new warnings - I have added tests that validates my changes, and provides sufficient test coverage. I have tested with: - Local testing - E2E testing in Teams - New and existing unit tests pass locally with my changes ### Additional information > Feel free to add other relevant information below --------- Co-authored-by: Corina <14900841+corinagum@users.noreply.github.com>
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Language
Javascript/Typescript, C#, Python
Version
latest
Description
I ran a broken link check on the repo and found that there are over 50 broken links some of which return HTTP error 404, 403.
Attaching the report file with this issue.
teams-ai-broken-links.txt
Reproduction Steps
npm install -g markdown-link-checkfor file in $(find . -type f -name '*.md'); do markdown-link-check "$file"; doneThe text was updated successfully, but these errors were encountered: