Remove stray token-like string from developer howto#250
Closed
Kunal241207 wants to merge 1 commit intosugarlabs:masterfrom
Closed
Remove stray token-like string from developer howto#250Kunal241207 wants to merge 1 commit intosugarlabs:masterfrom
Kunal241207 wants to merge 1 commit intosugarlabs:masterfrom
Conversation
Contributor
|
It's fine. Don't worry. It's an encrypted document identifier. It doesn't need explanation or precautions, because the audience for the document is developers who know or can guess what it is for. If someone has written something to worry about random strings then you need to patch that facility not the random string. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This removes the standalone string (
wi1meeL9Mahdeewu) from sugar-labs-developer-howto.txt.The string appears without context and resembles a token or credential. Even if not a secret, such unexplained strings can trigger automated security scanners and cause confusion for readers.
Removing it improves documentation clarity and avoids false positives.