-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Tech Writer: Redid Database Security Cheat Sheet #1330
Merged
Merged
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
hey @thornshadow99 good PR! Can you please fix last linter error: |
Hi there,
I don't know where that linter error is. I tried to find it but could not.
Could you help me? I'm just a tech writer. :)
Rob
…On Sun, Feb 18, 2024 at 11:08 AM mackowski ***@***.***> wrote:
hey @thornshadow99 <https://github.com/thornshadow99> good PR! Can you
please fix last linter error:
cheatsheets/Authentication_Cheat_Sheet.md:21:291 MD009/no-trailing-spaces
Trailing spaces [Expected: 0 or 2; Actual: 1]
—
Reply to this email directly, view it on GitHub
<#1330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDMXOULTQPA6GDHE5SXMZN3YUIROFAVCNFSM6AAAAABDNRLNJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGM3TEMRWGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
cheatsheets/Authentication_Cheat_Sheet.md:21:291 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]Like 21 row 29--Jim ***@***.***/manicodeSecure Coding EducationOn Feb 18, 2024, at 2:24 PM, RL Thornton ***@***.***> wrote:
Hi there,
I don't know where that linter error is. I tried to find it but could not.
Could you help me? I'm just a tech writer. :)
Rob
On Sun, Feb 18, 2024 at 11:08 AM mackowski ***@***.***> wrote:
hey @thornshadow99 <https://github.com/thornshadow99> good PR! Can you
please fix last linter error:
cheatsheets/Authentication_Cheat_Sheet.md:21:291 MD009/no-trailing-spaces
Trailing spaces [Expected: 0 or 2; Actual: 1]
—
Reply to this email directly, view it on GitHub
<#1330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDMXOULTQPA6GDHE5SXMZN3YUIROFAVCNFSM6AAAAABDNRLNJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGM3TEMRWGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because your review was requested.Message ID: ***@***.***>
|
Thanks!
…On Sun, Feb 18, 2024 at 5:48 PM Jim Manico ***@***.***> wrote:
cheatsheets/Authentication_Cheat_Sheet.md:21:291 MD009/no-trailing-spaces
Trailing spaces [Expected: 0 or 2; Actual: 1]Like 21 row 29--Jim
***@***.***/manicodeSecure Coding EducationOn Feb 18, 2024, at 2:24 PM, RL
Thornton ***@***.***> wrote:
Hi there,
I don't know where that linter error is. I tried to find it but could not.
Could you help me? I'm just a tech writer. :)
Rob
On Sun, Feb 18, 2024 at 11:08 AM mackowski ***@***.***> wrote:
> hey @thornshadow99 <https://github.com/thornshadow99> good PR! Can you
> please fix last linter error:
> cheatsheets/Authentication_Cheat_Sheet.md:21:291
MD009/no-trailing-spaces
> Trailing spaces [Expected: 0 or 2; Actual: 1]
>
> —
> Reply to this email directly, view it on GitHub
> <
#1330 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/BDMXOULTQPA6GDHE5SXMZN3YUIROFAVCNFSM6AAAAABDNRLNJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGM3TEMRWGM>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because your review was requested.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#1330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDMXOUOJAEQECAL37MFDDN3YUKALXAVCNFSM6AAAAABDNRLNJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGQ3TCNRQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I will merge that and fix linter in another PR :-) thanks @thornshadow99 for the update! |
Thanks. I will continue working on cheat sheets and I'll get ahold of
git--that's a promise. :)
Rob
…On Tue, Feb 20, 2024 at 3:43 AM mackowski ***@***.***> wrote:
Merged #1330 <#1330> into
master.
—
Reply to this email directly, view it on GitHub
<#1330 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDMXOUI5JA3VNMPYA5AIVM3YURO4TAVCNFSM6AAAAABDNRLNJOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHA2TQNBRG44DINY>
.
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.
Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series.
Please make sure that for your contribution:
[TEXT](URL)
If your PR is related to an issue, please finish your PR text with the following line:
This PR covers issue #.
Thank you again for your contribution 😃