1
0
mirror of synced 2025-12-23 21:07:12 -05:00

Deprecate GHES 3.1 (#28798)

* add 3.1 to deprecated versions

* rewrite img src to use azure blob storage in archive script

Co-authored-by: rachmari <rachmari@users.noreply.github.com>

* remove static files for ghes 3.1

* remove liquid conditionals and content for ghes 3.1

* remove outdated hardware reqs reusable

* Fix liquid conditional uncaught by script

* Close liquid conditionals missed by script

* Apply @mattpollard's suggestions

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>

Co-authored-by: rachmari <rachmari@users.noreply.github.com>
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
This commit is contained in:
Hector Alfaro
2022-07-11 17:17:09 -04:00
committed by GitHub
parent efaf5f825d
commit 95e6f3d3ab
672 changed files with 873 additions and 1047890 deletions

View File

@@ -30,4 +30,4 @@ $ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
> X-Poll-Interval: 60
```
Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).
Only events created within the past 90 days will be included in timelines. Events older than 90 days will not be included (even if the total number of events in the timeline is less than 300).

View File

@@ -75,4 +75,4 @@ xml:lang="en-US">
</content>
</entry>
</feed>
```
```

View File

@@ -19,3 +19,4 @@ children:
- /starring
- /watching
---

View File

@@ -58,4 +58,4 @@ Reason Name | Description
Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different.
For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again.
For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again.

View File

@@ -1,6 +1,6 @@
---
title: Starring
intro: 'The Starring API lets you bookmark a repository.'
intro: The Starring API lets you bookmark a repository.
versions:
fpt: '*'
ghes: '*'
@@ -29,4 +29,4 @@ There is one supported custom media type for the Starring REST API. When you use
application/vnd.github.star+json
For more information about media types, see "[Custom media types](/rest/overview/media-types)."
For more information about media types, see "[Custom media types](/rest/overview/media-types)."

View File

@@ -1,6 +1,6 @@
---
title: Watching
intro: "The Watching API lets users subscribe to notifications for activity in a repository."
intro: The Watching API lets users subscribe to notifications for activity in a repository.
versions:
fpt: '*'
ghes: '*'