Update assessment.md - FINAL Submission by Tamara Fine Skversky #2480
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-preliminary changes only-
|
Learn Build status updates of commit 28fed1c:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| data-explorer/kusto/query/assessment.md | Details |
data-explorer/kusto/query/assessment.md
- Line 24, Column 39: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#user-query-statements' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 25, Column 119: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#application-query-statements' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 46, Column 69: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#tabular-data-sources' in 'query/assessment.md'. - Line 24, Column 39: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#user-query-statements' will be broken in isolated environments. Replace with a relative link. - Line 24, Column 39: [Suggestion: preserve-view-not-set - See documentation]
You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#user-query-statements - Line 25, Column 119: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#application-query-statements' will be broken in isolated environments. Replace with a relative link. - Line 25, Column 119: [Suggestion: preserve-view-not-set - See documentation]
You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#application-query-statements - Line 77, Column 1: [Suggestion: table-syntax-invalid - See documentation]
Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
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
Here is a summary of the changes I made to this article: -Title: changed for clarity -Added "applies to" links at the top, which I saw in other articles and made sense here as well. -Intro: I trimmed it down significantly, and tried to remove jargon that seemed extraneous. I also employed content reuse, by taking some text from an existing article, and applying it here. It was preferable to the text that was in this version. I did make some light edits to the "lifted" text however. -Body of article: 1. I reordered the content, adding headings and subheadings, blockquotes (notes), code script, bullets, and so on where it seemed to improve clarity. 2. I removed details about management commands, as it seemed like a diversion from the main focus of the article. I instead put a link to more information about management commands in the references at the bottom. 3. I added bullets to the links in the KQL in other services 4. I corrected the References section title at the bottom, and at least 1 spelling error in one of the links. I also reordered these links slightly, in the hopes that it was a more intuitive order. 5. In Types of query statements, I added info I found in my research about the two types of statements... but tried to maintain focus in the article on the three (not two) types of user query statements. 6. I added some helper text introducing the example, and added a heading to that section as well, removing language that seemed too informal. Items I would have liked to have added with more time and knowledge: -Concrete examples of each user query statement types -A more thorough audit of the reference links, making sure anything relevant was included. Thank you for the opportunity.
Update assessment.md - Submission by Tamara
|
Learn Build status updates of commit 35e3775:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| data-explorer/kusto/query/assessment.md | Details |
data-explorer/kusto/query/assessment.md
- Line 24, Column 39: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#user-query-statements' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 25, Column 119: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#application-query-statements' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 24, Column 39: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#user-query-statements' will be broken in isolated environments. Replace with a relative link. - Line 24, Column 39: [Suggestion: preserve-view-not-set - See documentation]
You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#user-query-statements - Line 25, Column 119: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#application-query-statements' will be broken in isolated environments. Replace with a relative link. - Line 25, Column 119: [Suggestion: preserve-view-not-set - See documentation]
You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://learn.microsoft.com/en-us/kusto/query/statements?view=azure-data-explorer#application-query-statements - Line 57, Column 1: [Suggestion: table-syntax-invalid - See documentation]
Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
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
TFS-82
changed the title
|
Hello,
@microsoft-github-policy-service agree
Thank you!
…On Tue, Dec 10, 2024, 3:14 PM microsoft-github-policy-service[bot] < ***@***.***> wrote:
@TFS-82 <https://github.com/TFS-82> please read the following Contributor
License Agreement(CLA). If you agree with the CLA, please reply with the
following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
- (default - no company specified) I have sole ownership of
intellectual property rights to my Submissions and I am not making
Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
- (when company given) I am making Submissions in the course of work
for my employer (or my employer has intellectual property rights in my
Submissions by contract or applicable law). I have permission from my
employer to make Submissions and enter into this Agreement on behalf of my
employer. By signing below, the defined term “You” includes me and my
employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement Contribution License Agreement
This Contribution License Agreement (*“Agreement”*) is agreed to by the
party signing below (*“You”*),
and conveys certain license rights to Microsoft Corporation and its
affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is
effective as of the latest signature
date below.
1. *Definitions*.
*“Code”* means the computer software code, whether in human-readable
or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
*“Project”* means any of the projects owned or managed by Microsoft
and offered under a license
approved by the Open Source Initiative (www.opensource.org).
*“Submit”* is the act of uploading, submitting, transmitting, or
distributing code or other content to any
Project, including but not limited to communication on electronic
mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf
of, the Project for the purpose of
discussing and improving that Project, but excluding communication
that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
*“Submission”* means the Code and any other copyrightable material
Submitted by You, including any
associated comments and documentation.
2. *Your Submission*. You must agree to the terms of this Agreement
before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now
or in the future (except as
described in Section 4 below), Submit to any Project.
3. *Originality of Work*. You represent that each of Your Submissions
is entirely Your original work.
Should You wish to Submit materials that are not Your original work,
You may Submit them separately
to the Project if You (a) retain all copyright and license information
that was in the materials as You
received them, (b) in the description accompanying Your Submission,
include the phrase “Submission
containing materials of a third party:” followed by the names of the
third party and any licenses or other
restrictions of which You are aware, and (c) follow any other
instructions in the Project’s written
guidelines concerning Submissions.
4. *Your Employer*. References to “employer” in this Agreement include
Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a
contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your
employer has intellectual
property rights in Your Submission by contract or applicable law, You
must secure permission from Your
employer to make the Submission before signing this Agreement. In that
case, the term “You” in this
Agreement will refer to You and the employer collectively. If You
change employers in the future and
desire to Submit additional Submissions for the new employer, then You
agree to sign a new Agreement
and secure permission from the new employer before Submitting those
Submissions.
5. *Licenses*.
- *Copyright License*. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly
display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all
of the foregoing rights to third
parties.
- *Patent License*. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or
the combination of the
Submission with the Project to which it was Submitted to make, have
made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the
Project.
- *Other Rights Reserved*. Each party reserves all rights not
expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without
limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
6. *Representations and Warranties*. You represent that You are
legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your
original work (except as You may
have disclosed under Section 3). You represent that You have secured
permission from Your employer to
make the Submission in cases where Your Submission is made in the
course of Your work for Your
employer or Your employer has intellectual property rights in Your
Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You
represent and warrant that You
have the necessary authority to bind the listed employer to the
obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless
You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE
WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED
UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO,
ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. *Notice to Microsoft*. You agree to notify Microsoft in writing of
any facts or circumstances of which
You later become aware that would make Your representations in this
Agreement inaccurate in any
respect.
8. *Information about Submissions*. You agree that contributions to
Projects and information about
contributions may be maintained indefinitely and disclosed publicly,
including Your name and other
information that You submit with Your Submission.
9. *Governing Law/Jurisdiction*. This Agreement is governed by the
laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal
courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in
which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County,
Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
10. *Entire Agreement/Assignment*. This Agreement is the entire
agreement between the parties, and
supersedes any and all prior agreements, understandings or
communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may
be assigned by Microsoft.
—
Reply to this email directly, view it on GitHub
<#2480 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BNP3PKPTMJQUUVFZBJMWHJ32E3SKXAVCNFSM6AAAAABTK3OBYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZRGYYDGOBZGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@TFS-82 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
#hold-off |
|
You typed hold-off, but the PR wasn't signed off, so nothing was changed. |
|
Hi all,
Just making sure you don't need anything further from me here.
My PR was submitted as an assessment, and I signed as requested.
Perhaps I'm cc'ed on the latest messages by mistake?
Thx,
Tamara
…On Wed, Dec 11, 2024, 9:06 AM prmerger-automator[bot] < ***@***.***> wrote:
You typed hold-off, but the PR wasn't signed off, so nothing was changed.
—
Reply to this email directly, view it on GitHub
<#2480 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BNP3PKMUYFEF7Y7R33YURED2E7QATAVCNFSM6AAAAABTK3OBYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZTHAZDGMBRHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is a summary of the changes I made to this article (spanning two separate change commits):
Title changed for clarity
Beneath Title Added "applies to" links at the top, which I saw in other articles and made sense here as well.
Intro: I trimmed it down significantly, and tried to remove jargon that seemed extraneous. I also employed content reuse, by taking some text from an existing article, and applying it here. It was preferable to the text that was in this version. I did make some light edits to the "lifted" text however.
Body of article:
Items I would have liked to have added with more time and knowledge:
Note: I also debated about the title (using a colon, calling it "An Introduction", etc). "Overview" would have also worked, and I hesitated about capitalizing the word "An" after the intro, given sentence case convention.
In any case, I hope this submission meets your standards. Thank you so much for the opportunity.