* 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>
* ran script/remove-unused-assets.js (manually removed unused variables printed by the script)
* package-lock
* turn elsif into two ifs to prepare for running Liquid deprecation script
* ran script/remove-deprecated-enterprise-version-markup.js --release 2.14 (ONLY UPDATES LINE BREAKS ETC.)
* ran script/remove-deprecated-enterprise-version-markup.js --release 2.15
* ran script/remove-deprecated-enterprise-version-markup.js --release 2.17
* ran script/remove-deprecated-enterprise-version-markup.js --release 2.18
* update hardcoded test
* Update content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
* add currentVersion is NOT free-pro-team to conditional, to make sure the deprecation script does the right thing when it is time to deprecate 2.21
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
* Add back changes from prior to purge
* Fix tip syntax
* Revise conceptual introduction
* Use variable
* Revise "Further reading"
* Link out
* Add quotes
* Add prerequisites
* Move information out of note
* Simplify language
* Simplify further
* Evergreenify
* Tentatively remove section on overallocation
* Relocate more information; clean up
* Add permissions statement
* Use 'enterprise account'
* Cross-link
* Update linked content
* Mention pending invitations
* Move section
* Add introduction
* Flesh out conceptual introduction
* Remove "Further reading"; article in map topic
* Version link out for GitHub.com only
* Revert "Remove "Further reading"; article in map topic"
This reverts commit 6cfa72825878b3ee0662baaf1a215c4974563232.
* Remove correct section
* Run the site data tag script
* Fix typo
* Remove quotes
* Add missing word
* Break optional steps into ordered list items
* Add product; reorganize groupings
* Rename article; use Microsoft terminology
* Incorporate Winnie's feedback
* Deduplicate the spaces
* Simplify
* Use consistent terminology
* Revise introduction
* Revise further
* 🌲
* Incorporate more feedback from Winnie
* Add permissions statement
* Be explicit after all
* Actually, no, no permissions statement
* Fix typo
* Add prerequisite for clarity
Co-authored-by: Jason Etcovitch <jasonetco@github.com>
Co-authored-by: Meg Bird <megbird@github.com>
