* Check repository references
* Remove "foundRepoNames" that I used to find all the unique names
* A little speed up with Set
* Ignore a few files
* Remove remaining references
* Update README.md
* Improve documentation issue no #1034
Done with the minor fixes for open issue number #1034 .
* Increasing the importance
I wanted to delete a branch, but I couldn't in spite of reading this document. The problem was, the branch I wanted to delete was the default branch.
Even though it is stated in this document, it was not given enough importance that everyone would see it.
* typo
A small type in the comments
* Update setting-up-your-development-environment-to-create-a-github-app.md
Fix two small typos.
* properly capitalize "macOS"
* Clarify GH password requirements
* Change " to `
As done in the description of `master`
* " to ` in DE
* " to ` in PT
* " to ` in RU
* Fix typo metadata-syntax-for-github-actions.md
Fix typo for metadata-syntax-for-github-actions#outputs-for-composite-run-steps-actions
* chore: Remove bolding from headings
* Removed deprecated echo set-env instruction
* fix typo (#1516)
Co-authored-by: hubwriter <hubwriter@github.com>
* Remove extraneous grammar period which breaks the compare URL (#1252)
* Remove extraneous grammar period which breaks the compare URL
* Update data/reusables/repositories/two-dot-diff-comparison-example-urls.md
Co-authored-by: Nick Schonning <nschonni@gmail.com>
Co-authored-by: Nick Schonning <nschonni@gmail.com>
Co-authored-by: hubwriter <hubwriter@github.com>
* Revert "" to ` in RU"
This reverts commit d484fd6ef5.
* Revert "" to ` in PT"
This reverts commit fab62f05be.
* Revert "" to ` in DE"
This reverts commit 78abcd6f7a.
* Change md
This squashes all the translation commits and their deletion.
* Update content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md
Co-authored-by: Felicity Chapman <felicitymay@github.com>
Co-authored-by: Atharva Shirdhankar <72031540+StarTrooper08@users.noreply.github.com>
Co-authored-by: Aakarsh B <aakarshbiju@gmail.com>
Co-authored-by: Aritra Roy Gosthipaty <aritra.born2fly@gmail.com>
Co-authored-by: Guilherme Macedo <guilherme@gmacedo.com>
Co-authored-by: Stephen Wade <stephen@stephenwade.me>
Co-authored-by: Shao Yang Hong <hongsy2006@gmail.com>
Co-authored-by: a2br <62328077+a2br@users.noreply.github.com>
Co-authored-by: Cas van Dinter <casvd@hotmail.com>
Co-authored-by: Nick Schonning <nschonni@gmail.com>
Co-authored-by: Antoine Rondelet <rondelet.antoine@gmail.com>
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
Co-authored-by: Meg Bird <megbird@github.com>
Co-authored-by: ねず <39144575+wonda-tea-coffee@users.noreply.github.com>
Co-authored-by: hubwriter <hubwriter@github.com>
Co-authored-by: Ilia <ilia@wearebond.com>
Co-authored-by: a2br <a2br@users.noreply.github.com>
Co-authored-by: Felicity Chapman <felicitymay@github.com>
Co-authored-by: Jason Etcovitch <jasonetco@github.com>
* 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>
* Use conditioning to revert dismiss/delete alert changes on GHES
* Add new dotcom version text that is also good for GHES
* Reinstate original subheading for GHES 2.22
* Small update for change from head to merge commit for attribution
* Simplify the sentence about when codescan is run against PRs
Whether it does attribution using a comparison of the HEAD commit
or a merge into a temporary copy of the default branch
is too much information here.
* Use conditioning to revert dismiss/delete alert changes on GHES
* Add new dotcom version text that is also good for GHES
* Reinstate original subheading for GHES 2.22
Edited introductory paragraph and step 4 of the section to state that admin permissions are required to delete alerts.
Introductory paragraph changed to say, "Alternatively, if you have admin permissions for the repository, you can delete alerts."
and step 4 to "If you have admin permissions for the repository, and you want to delete alerts[...]"
Co-authored-by: hubwriter <54933897+hubwriter@users.noreply.github.com>
* Run script/new-versioning/update-not-fpt-conditionals.js
* Fix a few things
* Remove outdated versioning
* Fix broken link
Co-authored-by: jmarlena <6732600+jmarlena@users.noreply.github.com>
* Add new placeholder topic file - WiP
* Add content for new topic + cross-refs to it
* Change topic title just to get through the PR check for matching filename & title
* Rework the workflow example section
* Remove 4 lines from workflow - see:
https://github.com/github/code-scanning/issues/1826
* Updates for delete and dismiss alerts
* Add back the text for the now-deleted reusable
* Make s/shots relevant to the PR context of the text
* Make review comment changes
* More review comments attended to
* Restructure files and change topic titles and file names
* Update links to files whose names have changed
* Finish restructuring work for runner topics
* Makes changes suggested by James
* 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
* Manually fix some invalid Liquid
* Updoot render-content
* Improve test messages to show correct output
* Run el scripto
* Pass the remaining test
