diff --git a/content/actions/reference/limits.md b/content/actions/reference/limits.md index c76e61d3631e..0bb6be46a33c 100644 --- a/content/actions/reference/limits.md +++ b/content/actions/reference/limits.md @@ -40,6 +40,7 @@ These limits are subject to change. | Larger runners | Per runner concurrency limit | Varies by runner type | Established when setting up a runner. Normally 1,000 max for Linux CPU runners, but varies by type. See [Job concurrency limits for {% data variables.product.github %}-hosted runners](#job-concurrency-limits-for-github-hosted-runners). | {% octicon "check" aria-label="Yes" %} Support ticket | | Larger runners | Static IP limits | 10 IPs | 10 IPs per enterprise and organization. | {% octicon "check" aria-label="Yes" %} Support ticket | | Larger runners | Private IP scaling for vnet injection | 30% buffer | You need a buffer to accommodate the maximum job concurrency you anticipate. See [Private IP scaling for vnet injection on larger runners](#private-ip-scaling-for-vnet-injection-on-larger-runners). | {% octicon "check" aria-label="Yes" %} Configurable Azure virtual network | +| Dependency caching | Uploads per minute | 200 per minute | Each repository is limited to 200 cache entry uploads per minute. If this limit is exceeded, subsequent cache upload attempts will fail until the rate limit resets. | {% octicon "x" aria-label="No" %} | ### Job concurrency limits for {% data variables.product.github %}-hosted runners diff --git a/content/actions/reference/workflows-and-actions/dependency-caching.md b/content/actions/reference/workflows-and-actions/dependency-caching.md index 734f4c49d85f..d738959f92bd 100644 --- a/content/actions/reference/workflows-and-actions/dependency-caching.md +++ b/content/actions/reference/workflows-and-actions/dependency-caching.md @@ -229,14 +229,14 @@ For example, if a pull request contains a `feature` branch and targets the defau If you are caching the package managers listed below, using their respective setup-* actions requires minimal configuration and will create and restore dependency caches for you. -| Package managers | setup-* action for caching | -|---|---| -| npm, Yarn, pnpm | [setup-node](https://github.com/actions/setup-node#caching-global-packages-data) | -| pip, pipenv, Poetry | [setup-python](https://github.com/actions/setup-python#caching-packages-dependencies) | -| Gradle, Maven | [setup-java](https://github.com/actions/setup-java#caching-packages-dependencies) | -| RubyGems | [setup-ruby](https://github.com/ruby/setup-ruby#caching-bundle-install-automatically) | -| Go `go.sum` | [setup-go](https://github.com/actions/setup-go#caching-dependency-files-and-build-outputs) | -| .NET NuGet | [setup-dotnet](https://github.com/actions/setup-dotnet?tab=readme-ov-file#caching-nuget-packages) | +| Package managers | setup-* action for caching | +| ------------------- | ------------------------------------------------------------------------------------------------- | +| npm, Yarn, pnpm | [setup-node](https://github.com/actions/setup-node#caching-global-packages-data) | +| pip, pipenv, Poetry | [setup-python](https://github.com/actions/setup-python#caching-packages-dependencies) | +| Gradle, Maven | [setup-java](https://github.com/actions/setup-java#caching-packages-dependencies) | +| RubyGems | [setup-ruby](https://github.com/ruby/setup-ruby#caching-bundle-install-automatically) | +| Go `go.sum` | [setup-go](https://github.com/actions/setup-go#caching-dependency-files-and-build-outputs) | +| .NET NuGet | [setup-dotnet](https://github.com/actions/setup-dotnet?tab=readme-ov-file#caching-nuget-packages) | ## Restrictions for accessing a cache @@ -275,6 +275,8 @@ Multiple workflow runs in a repository can share caches. A cache created for a b {% endif %} {% ifversion fpt or ghec %} +You can create cache entries at a rate of up to 200 uploads per minute per repository. If you exceed this rate, subsequent cache upload attempts will fail until the rate limit resets. The time until the rate limit resets is returned in the `Retry-After` header of the response. + ### Increasing cache size If you want to reduce the rate at which cache entries are evicted, you can increase the storage limits for your cache in the Actions Settings. Repositories owned by users can configure up to 10 TB per repository. For repositories owned by organizations, the maximum configurable limit is determined by the organization's settings. For organizations owned by an enterprise, the maximum configurable limit is determined by the enterprise's settings. Increasing the limit beyond the default 10 GB will incur additional costs, if that storage is used. diff --git a/src/workflows/fr-add-docs-reviewers-requests.ts b/src/workflows/fr-add-docs-reviewers-requests.ts index e4decceb0f72..7b426be1e2d8 100644 --- a/src/workflows/fr-add-docs-reviewers-requests.ts +++ b/src/workflows/fr-add-docs-reviewers-requests.ts @@ -154,7 +154,7 @@ async function run() { // Get the ID of the fields that we want to populate const datePostedID = findFieldID('Date posted', projectData) - const targetDateID = findFieldID('Target Date', projectData) + const reviewDueDateID = findFieldID('Review due date', projectData) const statusID = findFieldID('Status', projectData) const featureID = findFieldID('Feature', projectData) const contributorTypeID = findFieldID('Contributor type', projectData) @@ -208,7 +208,7 @@ async function run() { statusID, statusValueID: readyForReviewID, datePostedID, - targetDateID, + reviewDueDateID, contributorTypeID, contributorType, sizeTypeID, diff --git a/src/workflows/projects.ts b/src/workflows/projects.ts index 8edc169dbe92..398b9e1924b8 100644 --- a/src/workflows/projects.ts +++ b/src/workflows/projects.ts @@ -181,7 +181,7 @@ export function calculateDueDate(datePosted: Date, turnaround = 2) { // generates a GraphQL mutation to populate: // - "Status" (as variable passed with the request) // - "Date posted" (as today) -// - "Target Date" (as today + {turnaround} weekdays) +// - "Review due date" (as today + {turnaround} weekdays) // - "Contributor type" (as variable passed with the request) // - "Feature" (as {feature}) // - "Author" (as {author})" @@ -241,7 +241,7 @@ export function generateUpdateProjectV2ItemFieldMutation({ $statusID: ID! $statusValueID: String! $datePostedID: ID! - $targetDateID: ID! + $reviewDueDateID: ID! $contributorTypeID: ID! $contributorType: String! $sizeTypeID: ID! @@ -264,7 +264,7 @@ export function generateUpdateProjectV2ItemFieldMutation({ })} ${generateMutationToUpdateField({ item, - fieldID: '$targetDateID', + fieldID: '$reviewDueDateID', value: formatDateForProject(dueDate), fieldType: 'date', literal: true, diff --git a/src/workflows/ready-for-docs-review.ts b/src/workflows/ready-for-docs-review.ts index 3d200994eadc..7eb15436dc33 100644 --- a/src/workflows/ready-for-docs-review.ts +++ b/src/workflows/ready-for-docs-review.ts @@ -134,7 +134,7 @@ async function run() { // Get the ID of the fields that we want to populate const datePostedID = findFieldID('Date posted', data) - const targetDateID = findFieldID('Target Date', data) + const reviewDueDateID = findFieldID('Review due date', data) const statusID = findFieldID('Status', data) const featureID = findFieldID('Feature', data) const contributorTypeID = findFieldID('Contributor type', data) @@ -263,7 +263,7 @@ async function run() { statusID, statusValueID: readyForReviewID, datePostedID, - targetDateID, + reviewDueDateID, contributorTypeID, contributorType, sizeTypeID,