Remove fake AWS secret #2541
Merged
Remove fake AWS secret #2541
Conversation
This file contains hidden or 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
Contributor
|
@samlevy-microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit d797dd3: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Contributor
|
#sign-off |
Contributor
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @shsagir |
shsagir
approved these changes
Feb 10, 2025
Collaborator
|
#sign-off |
prmerger-automator
bot
added
do-not-merge
and removed
qualifies-for-auto-merge
ready-to-merge
labels
Contributor
|
Learn Build status updates of commit d797dd3: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Contributor
Author
|
[like] Samuel Levy reacted to your message:
…________________________________
From: Courtney Wales ***@***.***>
Sent: Monday, February 10, 2025 4:43:01 PM
To: MicrosoftDocs/dataexplorer-docs ***@***.***>
Cc: Samuel Levy ***@***.***>; State change ***@***.***>
Subject: Re: [MicrosoftDocs/dataexplorer-docs] Remove fake AWS secret (PR #2541)
Merged #2541<#2541> into main.
—
Reply to this email directly, view it on GitHub<#2541 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKRG5EBTLABHHUA4OAIVROD2PDJJLAVCNFSM6AAAAABWZGIOZ6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJWGI2TCMJTGU4TAOA>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Thank you for contributing to Kusto documentation
Please add a brief comment outlining the purpose of this PR. Add links to any relevant references such as DevOps work items.
Make sure you've done the following:
Acrolinx: Make sure your Acrolinx score is at least 80 (higher is better) and with 0 spelling issues.
Successful build: Review the build status to make sure all files are green (Succeeded) and there are no errors, warnings, or suggestions.
Preview the pages: Click each Preview URL link, scan the entire page looking for formatting issues, in particular the parts you edited.
Check the Table of Contents: If you're adding a new markdown file, make sure it is linked from the table of contents.
Sign off: Once the PR is finalized, add a comment with
#sign-off. If you need to cancel the sign-off, add a comment with#hold-off.NOTE: Signing off means the document can be published at any time.
Next steps
Learn more about how to contribute