I suspect UI has changed in GHES since this docs were created, so I've updated them to match the UI in 2.22
Similar with Jira, the DVCS accounts are now under Applications
Lastly, Atlassian has changed "JIRA" to "Jira" a few years ago.
* Create basic layout
* Create stubbed out release note YAML
* Get a real implementation going
* Simplify using site-data
* Add a real page to send from render-page.js
* Use array of patches
* Render patches
* Add sidebar and breadcrumbs
* Reverse order
* Add date
* Tweak labels
* Redirect to entweb for missing versions
* Render patch.intro
* Move to separate files for patches
* Show support for RC versions
* Improve some comments
* Sticky headers!
* Remove a console log
* Improve example formatting
* Add a link on /admin
* Add a schema and test
* Move to /index.md, add version_num filter
* Improve layout
* Use <details>
* Placeholder more realistic notes
* Don't require links in index pages
* Remove admin/index link for now
* Remove unused frontmatter field
* Add a test for middleware
* Fix remaining YAML file to test CI
* Update 2-rc.yml
* Don't call it RC
* Just push
* Make a main a div
* Fix a borked class
* Lint YAML files
* Improve Download link
Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com>
* Improve check order
* Move to contextualizers
* Use alternative version thing
Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com>
* Move back to `release-notes.md`
* Use version for anchor IDs
* Undo category-pages test change
* Fix borked details layout in Chrome
* Improve mobile setup
* Render markdown in note tags
* Use allVersions[currentVersion] again
Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com>
* Undo change to extended-markdown
* Add whitespace so it renders markdown bits
* Remove 2-22 files
* Add check for any release notes
* Fix the failing tests
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com>
* Add the quickstart draft
* Add context for new article/support
* style tweaks
* add link to toc
* Small edits
* Детали!
* Add description
* Staging is my friend
* Apply suggestions from code review
* All about that space
* Formatting tweaks are almost there
* Balance is key.
* Last spacing attempts for now
* Another spacing adjustment
* Remove redirect
* Apply suggestions from code review
* Apply @lucascosti's stellar input
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
* spacing dance & Merge branch 'minio-setup-3067' of github.com:github/docs-internal into minio-setup-3067
* Apply @lucascosti's stellar input
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
* rewrite intro
* Fix intro
* Change order of intro
* intro tweak
* Apply suggestions from code review
Co-authored-by: Kayla Ngan <kaylangan@github.com>
* Apply URL example for next steps
* Tighten up text
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
Co-authored-by: Kayla Ngan <kaylangan@github.com>
Some tweaks to the verbiage around what is provided with Premium Support and GHAE.
Instead of the "Government notification box" indicating the TSAM will inform them of the difference, I propose a secondary article, similar to how we've setup Premium Support, with something like:
For more information, see "GitHub AE Support for Commercial and Government Cloud."
This new page should house all of the roles/responsibilities for each of the two respective services in a table format that's clear and defines the support offering better.
Also, while reviewing, this seems like it should be designated with "Cloud" to denote GHES and GHE**C**:
https://docs.github.com/en/enterprise-server@2.22/admin/enterprise-support/about-github-premium-support-for-github-enterprise
to "About GitHub Premium Support for GitHub Enterprise Cloud"
So we ultimately have:
About GitHub Premium Support for GitHub Enterprise Server
About GitHub Premium Support for GitHub Enterprise Cloud
About GitHub AE Support for Commercial and Government
The navigation would simply show the Commercial/Government Cloud page under "About GitHub Enterprise Support" in the navigation so the customers can see the differences in the two and we can better explain what we provide. Both of the "About Premium Support" pages expand on a lot of good information about Premium Support.
* first stab
* fix issues with liquid tags
* applied a few fixes and improvements
* rewrite options
* rewrite for GHES 2.21
* fix liquid versioning (again)
* I love liquid tags
* swap paragraphs for GHES 2.21
* add link to new article in 2 existing articles
* started major rework to avoid info duplication
* part of the reorg work
* starting the major reorg
* fix syntax
* rework Configuring notifications article
* reorganizing again
* more reorg
* add new reusable
* fix typo
* add correct variable
* link to correct article for GHES < 2.21
* Update content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
Co-authored-by: Alex Mullans <infin8x@github.com>
* Apply suggestions from code review
Co-authored-by: Felicity Chapman <felicitymay@github.com>
* Update data/reusables/notifications/vulnerable-dependency-notification-options-detailed.md
Co-authored-by: Maya Kaczorowski <15946341+mayakacz@users.noreply.github.com>
* fix typo reported in #16036
* address comments from code review
* yet another commit
* polishing
* Update content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md
Co-authored-by: Maya Kaczorowski <15946341+mayakacz@users.noreply.github.com>
* use variables
* address more comments
* add condition to link as linked article is free-pro-team only
* fix condition
* remove reusable that had duplicated content
* remove incorrect info
* fix issue in GHES article
* added shortTitle
* Apply suggestions from code review
Co-authored-by: Maya Kaczorowski <15946341+mayakacz@users.noreply.github.com>
* reword for clarity
* add more detail
Co-authored-by: Alex Mullans <infin8x@github.com>
Co-authored-by: Felicity Chapman <felicitymay@github.com>
Co-authored-by: Maya Kaczorowski <15946341+mayakacz@users.noreply.github.com>
* specify ssh shell
Specify that the command should be run within the administrative SSH shell, and link to the relevant document for access.
* Link to SSH doc as a note
* note syntrax
* remove extra space
* Update content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
Co-authored-by: hubwriter <54933897+hubwriter@users.noreply.github.com>
* Update enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
* Update enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md
* Indenting note box in markdown.
I should have spotted this in my previous review, so I'm going to go ahead and apply this change.
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>
