In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing content is larger than one hundred (100) repositories and thus would be difficult to review in its entirety, we may consider disabling the entire network if you state in your notice that, "Based on the representative number of forks you have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.

3. **Identify the material that you allege is infringing the copyrighted work listed in item #2, above.** It is important to be as specific as possible in your identification. This identification needs to be reasonably sufficient to permit GitHub to locate the material. At a minimum, this means that you should include the URL to the material allegedly infringing your copyright. If you allege that less than a whole repository infringes, identify the specific file(s) or line numbers within a file that you allege infringe. If you allege that all of the content at a URL infringes, please be explicit about that as well.

- Please note that GitHub will *not* automatically disable [forks](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) when disabling a parent repository. If you have investigated and analyzed the forks of a repository and believe that they are also infringing, please explicitly identify each allegedly infringing fork. Please also confirm that you have investigated each individual case and that your sworn statements apply to each identified fork. In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing content is larger than one hundred (100) repositories and thus would be difficult to review in its entirety, we may consider disabling the entire network if you state in your notice that, "Based on the representative number of forks you have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.

const lastVersionWithoutArchivedRedirectsFile = '2.17'

lastVersionWithoutArchivedRedirectsFile,

// Only add this configuration for TLS-enabled REDIS_URL values.

// Otherwise, it breaks for local Redis instances without TLS enabled.

...REDIS_URL.startsWith('rediss://') && {

tls: {

// Required for production Heroku Redis

rejectUnauthorized: false

}

"gravatar_id": "",

"url": "https://api.github.com/users/github",

"followers_url": "https://api.github.com/users/github/followers",

"following_url": "https://api.github.com/users/github/following{/other_user}",

"gists_url": "https://api.github.com/users/github/gists{/gist_id}",

"starred_url": "https://api.github.com/users/github/starred{/owner}{/repo}",

"subscriptions_url": "https://api.github.com/users/github/subscriptions",

"organizations_url": "https://api.github.com/users/github/orgs",

"repos_url": "https://api.github.com/users/github/repos",

"events_url": "https://api.github.com/users/github/events{/privacy}",

"received_events_url": "https://api.github.com/users/github/received_events",

"type": "Organization",

"site_admin": false

const { firstVersionDeprecatedOnNewSite, lastVersionWithoutArchivedRedirectsFile } = require('../lib/enterprise-server-releases')

// starting with 2.18, we updated the archival script to create a redirects.json file

versionSatisfiesRange(requestedVersion, `<=${lastVersionWithoutArchivedRedirectsFile}`)) {

let reqPath = req.path

let isRedirect = false

if (versionSatisfiesRange(requestedVersion, `>${lastVersionWithoutArchivedRedirectsFile}`)) {

try {

const res = await got(getProxyPath('redirects.json', requestedVersion))

const redirectJson = JSON.parse(res.body)

if (redirectJson[req.path]) {

isRedirect = true

}

reqPath = redirectJson[req.path] || req.path

} catch (err) {

// nooop

}

}

const r = await got(getProxyPath(reqPath, requestedVersion))

// make redirects found via redirects.json return 301 instead of 200

if (isRedirect) {

res.status(301)

res.set('location', reqPath)

}

// make stubbed redirect files (which exist in versions <2.13) return 301 instead of 200

if (versionSatisfiesRange(requestedVersion, `>${lastVersionWithoutArchivedRedirectsFile}`)) return

// Only add this configuration for TLS-enabled REDIS_URL values.

// Otherwise, it breaks for local Redis instances without TLS enabled.

...REDIS_URL.startsWith('rediss://') && {

tls: {

// Required for production Heroku Redis

rejectUnauthorized: false

}

await createRedirectsFile(permalinksPerVersion, pageMap, finalDirectory)

async function createRedirectsFile (permalinks, pageMap, finalDirectory) {

const redirectsPerVersion = {}

redirectsPerVersion[oldPath] = newPath

fs.writeFileSync(path.posix.join(finalDirectory, 'redirects.json'), JSON.stringify(redirectsPerVersion, null, 2))

// Only add this configuration for TLS-enabled REDIS_URL values.

// Otherwise, it breaks for local Redis instances without TLS enabled.

...REDIS_URL.startsWith('rediss://') && {

tls: {

// Required for production Heroku Redis

rejectUnauthorized: false

}

test('can access redirects from redirects.json in deprecated enterprise content >2.17', async () => {

const res = await get('/enterprise/2.19/admin/categories/time')

expect(res.statusCode).toBe(301)

expect(res.headers.location).toBe('/en/enterprise-server@2.19/admin/configuration/configuring-time-synchronization')

})