* Changed 'people' to 'accounts'
Adding some precision: Changed 'People with write permission to a repository can manage' to 'Accounts with write permission to a repository can manage"
People don't have permission; accounts have permission.
* edits for clarity
* clarity
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
Co-authored-by: hubwriter <54933897+hubwriter@users.noreply.github.com>
Co-authored-by: hubwriter <54933897+hubwriter@users.noreply.github.com>
* Add more information to the codescan enabling topic - WiP
* Add more details and s/shots to the Enabling topic
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Make change suggested by Justin, but in step 5 rather than step 4.
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Not all workflows will have `on:push` and `on:pull_request` so clarify that this refers to the CodeQL workflow.
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Revert changes to this file to the file as it currently is on main
* Attempt to remove package.json
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
Co-authored-by: Chiedo <chiedo@users.noreply.github.com>
Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com>
* Add back changes from prior to purge
* Manually fix some invalid Liquid
* Updoot render-content
* Improve test messages to show correct output
* Run el scripto
* Pass the remaining test
