diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index fa6f7887b756..af401fbc2435 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -38,7 +38,7 @@ Commits will appear on your contributions graph if they meet **all** of the foll * In the repository's default branch * In the `gh-pages` branch (for repositories with project sites) -For more information on project sites, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites). +For more information on project sites, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites). In addition, **at least one** of the following must be true: * You are a collaborator on the repository or are a member of the organization that owns the repository. @@ -83,7 +83,7 @@ Generic email addresses, such as `jane@computer.local`, cannot be added to {% da ### Commit was not made in the default or `gh-pages` branch -Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites). +Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites). If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following: * [Open a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch. diff --git a/content/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts.md b/content/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts.md index 69b87ec9501c..9aee84f2ee44 100644 --- a/content/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts.md +++ b/content/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts.md @@ -54,7 +54,7 @@ With {% data variables.product.prodname_emus %}, you can control the user accoun ## {% data variables.product.prodname_pages %} -* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. See [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users). +* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. See [AUTOTITLE](/pages/getting-started-with-github-pages/github-pages-limits#limits-for-enterprise-managed-users). ## Interactions diff --git a/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index e98606b18d99..fc0a19bdaacb 100644 --- a/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -138,11 +138,17 @@ After using `git-filter-repo` to remove the sensitive data and pushing your chan 1. Contact {% data variables.contact.contact_support %}, and provide the following information: * The owner and repository name in question (e.g. YOUR-USERNAME/YOUR-REPOSITORY). +{%- ifversion fpt or ghec %} * The number of affected pull requests, found in the previous step. This is used by Support to verify you understand how much will be affected. +{%- endif %} +{%- ifversion ghes %} + * The number of affected pull requests, found in the previous step. This is used by your site administrator to verify you understand how much will be affected. +{%- endif %} * The First Changed Commit(s) reported by `git-filter-repo` (Look for `NOTE: First Changed Commit(s)` in its output.) * If `NOTE: There were LFS Objects Orphaned by this rewrite` appears in the git-filter-repo output (right after the First Changed Commit), then mention you had LFS Objects Orphaned and upload the named file to the ticket as well. - If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then: + {% ifversion fpt or ghec %}If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then:{% endif %} + {% ifversion ghes %}If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, your site administrator will then:{% endif %} * Dereference or delete any affected PRs on {% data variables.product.github %}. * Run a garbage collection on the server to expunge the sensitive data from storage. diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md index 3b2a02024ee0..046088235138 100644 --- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md +++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md @@ -35,12 +35,6 @@ body: You can set the following top-level keys for each issue form. -{% ifversion issue-types %} - -{% data reusables.issues.release-stage %} - -{% endif %} - | Key | Description | Required | Type | | :-- | :-- | :-- | :-- | | `name` | A name for the issue form template. Must be unique from all other templates, including Markdown templates. | Required | String | diff --git a/content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md b/content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md index dacb7c244e3a..4d9b6ee3f604 100644 --- a/content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md +++ b/content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md @@ -14,9 +14,14 @@ redirect_from: - /copilot/github-copilot-enterprise/overview/enabling-github-copilot-enterprise-features --- -## 1. Subscribe your enterprise to {% data variables.product.prodname_copilot %} +## 1. Enable {% data variables.product.prodname_copilot %} in your Enterprise through payment verification -Set up a subscription to {% data variables.product.prodname_copilot_enterprise_short %} or {% data variables.product.prodname_copilot_business_short %} for your enterprise. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/subscribing-to-copilot-for-your-enterprise). +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +1. Click the **{% octicon "check-circle" aria-hidden="true" %} Getting Started** tab. +1. Under "Next steps", click **Verify your payment method**. This will enable {% data variables.product.prodname_copilot %} in your enterprise. + +After you've completed these steps, you will be able to confirm that {% data variables.product.prodname_copilot %} is enabled in your enterprise's **{% octicon "law" aria-hidden="true" %} Policies** tab. ## 2. Set policies diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md index 3243957bc50a..a65011decffc 100644 --- a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md +++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md @@ -233,8 +233,6 @@ You can also use a * as a wildcard. If your organization uses issue types, you can filter for particular types. -{% data reusables.issues.release-stage %} - | Qualifier | Example | ---------- | ------------- | type:"ISSUE TYPE" | **type:"bug"** will show issues with the "bug" type. @@ -247,8 +245,6 @@ If your organization uses issue types, you can filter for particular types. You can filter your sub-issues by their parent issue. -{% data reusables.issues.release-stage %} - | Qualifier | Example | ---------- | ------------- | parent-issue:OWNER/REPO#ISSUE NUMBER | **parent-issue:octocat/game#4** will show issues with issue #4 in octocat/game as their parent issue. diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md b/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md index 480e58786bdb..73b07b7be042 100644 --- a/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md +++ b/content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md @@ -10,8 +10,6 @@ shortTitle: 'Managing issue types' permissions: 'Organization owners can modify issue types.' --- -{% data reusables.issues.release-stage %} - You can use issue types to classify and manage different types of issues across your organization. You can create up to {% data variables.projects.issue_type_limit %} issue types that your organization members can apply to issues, making it easier for you and your members to find issues and plan work. Default issue types are included in every organization, but these can edited, disabled, or deleted. The default types are task, bug, and feature. diff --git a/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md b/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md index 75797d201dcd..5f6b8fe95284 100644 --- a/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md +++ b/content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md @@ -88,8 +88,6 @@ Below we have added a task list to our Project Octocat issue, breaking it down i ### Breaking down your work with sub-issues -{% data reusables.issues.release-stage %} - {% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues). {% endif %} diff --git a/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md b/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md index 4eb1fb4fa202..25bd5a6c6f21 100644 --- a/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md +++ b/content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md @@ -42,8 +42,6 @@ You can also make changes to the issue description. The edit history is availabl ## Adding or changing the issue type -{% data reusables.issues.release-stage %} - You can add an issue type or make changes to an existing issue type. 1. Navigate to the issue you want to edit. diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md index aa9d7e4fb4f9..bb96793d39e9 100644 --- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md +++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -34,7 +34,7 @@ We recommend always using a `www` subdomain, even if you also use an apex domain ## Using a custom domain across multiple repositories -If you set a custom domain for a user or organization site, by default, the same custom domain will be used for all project sites owned by the same account. For more information about site types, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites). +If you set a custom domain for a user or organization site, by default, the same custom domain will be used for all project sites owned by the same account. For more information about site types, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites). For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`. diff --git a/content/pages/getting-started-with-github-pages/about-github-pages.md b/content/pages/getting-started-with-github-pages/about-github-pages.md deleted file mode 100644 index 3190278eda25..000000000000 --- a/content/pages/getting-started-with-github-pages/about-github-pages.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -title: About GitHub Pages -intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /articles/what-are-github-pages - - /articles/what-is-github-pages - - /articles/user-organization-and-project-pages - - /articles/using-a-static-site-generator-other-than-jekyll - - /articles/mime-types-on-github-pages - - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio - - /articles/about-github-pages - - /github/working-with-github-pages/about-github-pages - - /early-access/github/articles/managing-your-disabled-github-pages-site -product: '{% data reusables.gated-features.pages %}' -versions: - fpt: '*' - ghes: '*' - ghec: '*' -topics: - - Pages ---- - -## About {% data variables.product.prodname_pages %} - -{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.github %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples). - -{% ifversion fpt or ghec %} -You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. For more information, see [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site). -{% endif %} - -{% ifversion fpt or ghec %} -{% data reusables.pages.about-private-publishing %} For more information, see [Changing the visibility of your {% data variables.product.prodname_pages %} site]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site){% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} -{% endif %} - -To get started, see [AUTOTITLE](/pages/getting-started-with-github-pages/creating-a-github-pages-site). - -Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization). - -## Types of {% data variables.product.prodname_pages %} sites - -There are three types of {% data variables.product.prodname_pages %} sites: project, user, and organization. Project sites are connected to a specific project hosted on {% data variables.product.github %}, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific account on {% data variables.location.product_location %}. - -* User sites are hosted in a repository owned by your personal account, named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. -* Organization sites are hosted in a repository owned by an organization, named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. - -{% ifversion fpt or ghec %}Unless you're using a custom domain, user and organization sites are available at `http(s)://.github.io` or `http(s)://.github.io`.{% endif %} - -{% data reusables.pages.twenty-minutes-to-publish %} - -The source files for a project site are stored in the same repository as their project. {% ifversion fpt or ghec %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% endif %} - -{% ifversion ghec %} -If you publish your site privately, the URL for your site will be different. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site). -{% endif %} - -{% ifversion fpt or ghec %} -For more information about how custom domains affect the URL for your site, see [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages#using-a-custom-domain-across-multiple-repositories). -{% endif %} - -You can only create one user or organization site for each account on {% data variables.product.github %}. Project sites, whether owned by an organization or a personal account, are unlimited. - -{% ifversion ghes %} -The URL where your site is available depends on whether subdomain isolation is enabled for {% data variables.location.product_location %}. - -| Type of site | Subdomain isolation enabled | Subdomain isolation disabled | -| ------------ | --------------------------- | ---------------------------- | -User | `http(s)://pages./` | `http(s):///pages/` | -Organization | `http(s)://pages./` | `http(s):///pages/` | -Project site owned by personal account | `http(s)://pages.///` | `http(s):///pages///` -Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` - -For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation) or contact your site administrator. -{% endif %} - -## Publishing sources for {% data variables.product.prodname_pages %} sites - -{% data reusables.pages.private_pages_are_public_warning %} - -{% data reusables.pages.pages-about-publishing-source %} - -For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). - -{% ifversion ghec %} - -## Limitations for {% data variables.product.prodname_emus %} - -If you're a {% data variables.enterprise.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited. - -* {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations. -* {% data variables.product.prodname_pages %} sites are always privately published, and you cannot change this visibility. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site). -* You cannot create an organization site (a site published from a repository named `.github.io`) - -For more information about {% data variables.product.prodname_emus %}, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users). -{% endif %} - -## Static site generators - -{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. - -If you use a custom build process or a static site generator other than Jekyll, you can write a {% data variables.product.prodname_actions %} to build and publish your site. {% data variables.product.github %} provides workflow templates for several static site generators. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). - -If you publish your site from a source branch, {% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, we recommend that you write a {% data variables.product.prodname_actions %} to build and publish your site instead. Otherwise, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. - -{% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python. - -## Limits on use of {% data variables.product.prodname_pages %} - -{% ifversion fpt or ghec %} -{% data variables.product.prodname_pages %} sites created after June 15, 2016, and using `github.io` domains are served over HTTPS. If you created your site before June 15, 2016, you can enable HTTPS support for traffic to your site. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https). - -### Prohibited uses - -{% endif %} -{% data variables.product.prodname_pages %} is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). {% data reusables.pages.no_sensitive_data_pages %} - -In addition, your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/free-pro-team@latest/site-policy/github-terms/github-terms-of-service), including the restrictions on get-rich-quick schemes, sexually obscene content, and violent or threatening content or activity. - -### Educational exercises - -Using {% data variables.product.prodname_pages %} to create a copy of an existing website as a learning exercise is not prohibited. However, in addition to complying with the [GitHub Terms of Service](/free-pro-team@latest/site-policy/github-terms/github-terms-of-service), you must write the code yourself, the site must not collect any user data, and you must include a prominent disclaimer on the site indicating that the project is not associated with the original and was only created for educational purposes. - -### Usage limits - -{% data variables.product.prodname_pages %} sites are subject to the following usage limits: - -* {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB.{% ifversion fpt or ghec %} For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-and-repository-size-limitations){% endif %}. -* Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB. -* {% data variables.product.prodname_pages %} deployments will timeout if they take longer than 10 minutes. -{% ifversion fpt or ghec %} -* {% data variables.product.prodname_pages %} sites have a _soft_ bandwidth limit of 100 GB per month. -* {% data variables.product.prodname_pages %} sites have a _soft_ limit of 10 builds per hour. This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow. -* In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body. - -If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.github_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. - -{% endif %} - -## MIME types on {% data variables.product.prodname_pages %} - -A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db). - -While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types). - -{% ifversion fpt %} - -## Data collection - -When a {% data variables.product.prodname_pages %} site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into {% data variables.product.prodname_dotcom %} or not. For more information about {% data variables.product.prodname_dotcom %}'s security practices, see [{% data variables.product.prodname_dotcom %} Privacy Statement](/site-policy/privacy-policies/github-privacy-statement). -{% endif %} - -## Further reading - -* [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %} -* [AUTOTITLE](/rest/repos#pages) diff --git a/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index fa9e9774647d..3aa0c85a43db 100644 --- a/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -15,11 +15,11 @@ With access control for {% data variables.product.prodname_pages %}, you can res {% data reusables.pages.privately-publish-ghec-only %} -If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. For more information about {% data variables.product.prodname_emus %}, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users). +If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. For more information about {% data variables.product.prodname_emus %}, see [AUTOTITLE](/pages/getting-started-with-github-pages/github-pages-limits#limits-for-enterprise-managed-users). If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your project sites privately or publicly to anyone on the internet. -Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites). +Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites). ## About subdomains for privately published sites diff --git a/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md index 8cc4bc299693..1eb27c097828 100644 --- a/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md +++ b/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -35,35 +35,56 @@ shortTitle: Create a GitHub Pages site ## Creating your site {% data reusables.pages.must-have-repo-first %} - {% data reusables.pages.private_pages_are_public_warning %} - {% data reusables.pages.navigate-site-repo %} -{% data reusables.pages.decide-publishing-source %} +1. Decide which publishing source you want to use. See [AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). 1. Create the entry file for your site. {% data variables.product.prodname_pages %} will look for an `index.html`, `index.md`, or `README.md` file as the entry file for your site. If your publishing source is a branch and folder, the entry file must be at the top level of the source folder on the source branch. For example, if your publishing source is the `/docs` folder on the `main` branch, your entry file must be located in the `/docs` folder on a branch called `main`. If your publishing source is a {% data variables.product.prodname_actions %} workflow, the artifact that you deploy must include the entry file at the top level of the artifact. Instead of adding the entry file to your repository, you may choose to have your {% data variables.product.prodname_actions %} workflow generate your entry file when the workflow runs. -{% data reusables.pages.configure-publishing-source %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.pages.sidebar-pages %} -{% data reusables.pages.choose-visibility %} -{% data reusables.pages.visit-site %} +1. Configure your publishing source. See [AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). {% data reusables.pages.check-workflow-run %} +## Viewing your published site + +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{%- ifversion ghec %} +1. Optionally, if you're publishing a project site from a private or internal repository, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the visibility dropdown menu, then select public or private. + ![Screenshot of Pages settings for a repository. The visibility dropdown, currently set to "Private," is outlined in dark orange.](/assets/images/help/pages/public-or-private-visibility.png) + {% indented_data_reference reusables.pages.privately-publish-ghec-only spaces=3 %} +{%- endif %} +1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" %} Visit site**. + +{% data reusables.pages.twenty-minutes-to-publish %} {% data reusables.pages.admin-must-push %} +## Static site generators + +{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. + +If you use a custom build process or a static site generator other than Jekyll, you can write a {% data variables.product.prodname_actions %} workflow to build and publish your site. {% data variables.product.github %} provides workflow templates for several static site generators. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). + +If you publish your site from a source branch, {% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, we recommend that you write a {% data variables.product.prodname_actions %} to build and publish your site instead. Otherwise, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. + +>[!NOTE] {% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python. + +## MIME types on {% data variables.product.prodname_pages %} + +A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db). + +While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types). + ## Next steps You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% ifversion fpt or ghec %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html`. You can also add a theme to customize your site’s look and feel. For more information, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll). -To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll). - ## Further reading +* [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll). * [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites) * [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository) * [AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files) diff --git a/content/pages/getting-started-with-github-pages/github-pages-limits.md b/content/pages/getting-started-with-github-pages/github-pages-limits.md new file mode 100644 index 000000000000..a9cf0c64392a --- /dev/null +++ b/content/pages/getting-started-with-github-pages/github-pages-limits.md @@ -0,0 +1,50 @@ +--- +title: GitHub Pages limits +intro: 'Learn about the limits and limitations of GitHub Pages.' +product: '{% data reusables.gated-features.pages %}' +versions: + fpt: '*' + ghes: '*' + ghec: '*' +topics: + - Pages +--- + +## Usage limits + +{% data variables.product.prodname_pages %} is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). {% data reusables.pages.no_sensitive_data_pages %} + +In addition, your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/free-pro-team@latest/site-policy/github-terms/github-terms-of-service), including the restrictions on get-rich-quick schemes, sexually obscene content, and violent or threatening content or activity. + +{% data variables.product.prodname_pages %} sites are subject to the following usage limits: + +* You can only create one user or organization site for each account on {% data variables.product.github %}. +* {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB. {% ifversion fpt or ghec %}For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-and-repository-size-limitations){% endif %}. +* Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB. +* {% data variables.product.prodname_pages %} deployments will timeout if they take longer than 10 minutes. +{% ifversion fpt or ghec %} +* {% data variables.product.prodname_pages %} sites have a _soft_ bandwidth limit of 100 GB per month. +* {% data variables.product.prodname_pages %} sites have a _soft_ limit of 10 builds per hour. This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow. +* In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body. + +If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.github_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. + +{% endif %} + +{% ifversion ghec %} + +## Limits for {% data variables.product.prodname_emus %} + +If you're a {% data variables.enterprise.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited. + +* {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations. +* {% data variables.product.prodname_pages %} sites are always privately published, and you cannot change this visibility. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site). +* You cannot create an organization site (a site published from a repository named `.github.io`) + +For more information about {% data variables.product.prodname_emus %}, see [AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users). + +{% endif %} + +## Educational exercises + +Using {% data variables.product.prodname_pages %} to create a copy of an existing website as a learning exercise is not prohibited. However, in addition to complying with the [GitHub Terms of Service](/free-pro-team@latest/site-policy/github-terms/github-terms-of-service), you must write the code yourself, the site must not collect any user data, and you must include a prominent disclaimer on the site indicating that the project is not associated with the original and was only created for educational purposes. diff --git a/content/pages/getting-started-with-github-pages/index.md b/content/pages/getting-started-with-github-pages/index.md index fd77c4a345e8..c5e953bbd6c3 100644 --- a/content/pages/getting-started-with-github-pages/index.md +++ b/content/pages/getting-started-with-github-pages/index.md @@ -14,8 +14,9 @@ versions: topics: - Pages children: - - /about-github-pages + - /what-is-github-pages - /creating-a-github-pages-site + - /github-pages-limits - /using-custom-workflows-with-github-pages - /configuring-a-publishing-source-for-your-github-pages-site - /deleting-a-github-pages-site diff --git a/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index c98be324fba8..2c87203c68b8 100644 --- a/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -19,6 +19,8 @@ People with admin permissions for a repository can enforce HTTPS for a {% data v All {% data variables.product.prodname_pages %} sites, including sites that are correctly configured with a custom domain, support HTTPS and HTTPS enforcement. For more information about custom domains, see [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages) and [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages#https-errors). +{% data variables.product.prodname_pages %} sites created after June 15, 2016, and using `github.io` domains are served over HTTPS automatically. + {% data reusables.pages.no_sensitive_data_pages %} {% data reusables.pages.private_pages_are_public_warning %} diff --git a/content/pages/getting-started-with-github-pages/what-is-github-pages.md b/content/pages/getting-started-with-github-pages/what-is-github-pages.md new file mode 100644 index 000000000000..728192fbd183 --- /dev/null +++ b/content/pages/getting-started-with-github-pages/what-is-github-pages.md @@ -0,0 +1,100 @@ +--- +title: 'What is {% data variables.product.prodname_pages %}?' +intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% data variables.product.prodname_dotcom %}.' +allowTitleToDifferFromFilename: true +redirect_from: + - /articles/what-is-github-pages + - /articles/user-organization-and-project-pages + - /articles/using-a-static-site-generator-other-than-jekyll + - /articles/mime-types-on-github-pages + - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio + - /articles/about-github-pages + - /github/working-with-github-pages/about-github-pages + - /early-access/github/articles/managing-your-disabled-github-pages-site + - /pages/getting-started-with-github-pages/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + fpt: '*' + ghes: '*' + ghec: '*' +topics: + - Pages +--- + +## About {% data variables.product.prodname_pages %} + +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.github %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples). + +## Types of {% data variables.product.prodname_pages %} sites + +There are two types of {% data variables.product.prodname_pages %} sites. Sites associated with a user or organization account, and sites for a specific project. + + + + + + + + + + + + + + + + + + + + +{% ifversion fpt or ghec %} + + + + + +{% else %} + + + + + + + + + + +{% endif %} + +
PropertyUser and organization sitesProject sites
Source filesMust be stored in a repository named <owner>.github.io, where <owner> is the personal or organization account nameStored in a folder within the repository that contains the project's code
LimitsMaximum of one pages site per accountMaximum of one pages site per repository
Default site locationhttp(s)://<owner>.github.iohttp(s)://<owner>.github.io/<repositoryname>
Default site location with subdomain isolation enabledhttp(s)://pages.<hostname>/<owner>http(s)://pages.<hostname>/<owner>/<repository>/
Default site location with subdomain isolation disabledhttp(s)://<hostname>/pages/<username>http(s)://<hostname>/pages/<owner>/<repository>/
+ +{% ifversion ghec %} +If you publish your site privately, the URL for your site will be different. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site). +{% endif %} + +{% ifversion ghes %} +For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation) or contact your site administrator. +{% endif %} + +{% ifversion fpt or ghec %} + +### Hosting on your own custom domain + +You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. See [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site). + +{% endif %} + +{% ifversion fpt %} + +## Data collection + +When a {% data variables.product.prodname_pages %} site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into {% data variables.product.prodname_dotcom %} or not. For more information about {% data variables.product.prodname_dotcom %}'s security practices, see [{% data variables.product.prodname_dotcom %} Privacy Statement](/site-policy/privacy-policies/github-privacy-statement). +{% endif %} + +## Further reading + +* [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %} +* [AUTOTITLE](/rest/repos#pages) +* [AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site) +{% ifversion fpt or ghec %} * [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages#using-a-custom-domain-across-multiple-repositories) {% endif %} diff --git a/content/pages/index.md b/content/pages/index.md index 03976f514af5..1680674523e5 100644 --- a/content/pages/index.md +++ b/content/pages/index.md @@ -4,7 +4,7 @@ shortTitle: "{% data variables.product.prodname_pages %}" intro: 'Learn how to create a website directly from a repository on {% data variables.product.prodname_dotcom %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' introLinks: quickstart: /pages/quickstart - overview: /pages/getting-started-with-github-pages/about-github-pages + overview: /pages/getting-started-with-github-pages/what-is-github-pages featuredLinks: startHere: - /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site diff --git a/content/pages/quickstart.md b/content/pages/quickstart.md index 8868bc5a22d0..afb15062ec49 100644 --- a/content/pages/quickstart.md +++ b/content/pages/quickstart.md @@ -15,9 +15,7 @@ product: '{% data reusables.gated-features.pages %}' ## Introduction -{% data variables.product.prodname_pages %} are public webpages hosted and published through {% data variables.product.github %}. The quickest way to get up and running is by using the Jekyll Theme Chooser to load a pre-made theme. You can then modify your {% data variables.product.prodname_pages %}' content and style. - -This guide will lead you through creating a user site at `username.github.io`. +In this guide, you'll create a user site at `.github.io`. ## Creating your website @@ -50,10 +48,11 @@ By default, the title of your site is `username.github.io`. You can change the t description: Bookmark this to keep an eye on my project updates! ``` -1. When you are done editing the file, click **Commit changes**. +1. When you are finished editing the file, click **Commit changes**. ## Next Steps -For more information about how to add additional pages to your site, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll#about-content-in-jekyll-sites). +You've successfully created, personalized, and published your first {% data variables.product.prodname_pages %} website but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_pages %}: -For more information about setting up a {% data variables.product.prodname_pages %} site with Jekyll, see [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll). +* [AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll#about-content-in-jekyll-sites): This guide explains how to add additional pages to your site. +{% ifversion fpt or ghec %}* [AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site): You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain.{% endif %} diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md index 327341b8d098..ce0a0dc9cb8f 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -34,7 +34,7 @@ Jekyll is a static site generator with built-in support for {% data variables.pr Jekyll is not officially supported for Windows. For more information, see [Jekyll on Windows](https://jekyllrb.com/docs/windows/#installation) in the Jekyll documentation. -We recommend using Jekyll with {% data variables.product.prodname_pages %}. If you prefer, you can use other static site generators or customize your own build process locally or on another server. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#static-site-generators). +We recommend using Jekyll with {% data variables.product.prodname_pages %}. If you prefer, you can use other static site generators or customize your own build process locally or on another server. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/creating-a-github-pages-site#static-site-generators). ## Configuring Jekyll in your {% data variables.product.prodname_pages %} site diff --git a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md index c6f801299941..7e803588b7e2 100644 --- a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md +++ b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md @@ -19,7 +19,7 @@ When you rename a repository, all existing information, with the exception of pr * Stars * Followers -For more information on project sites, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites). +For more information on project sites, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites). In addition to redirecting web traffic, all `git clone`, `git fetch`, or `git push` operations targeting the previous location will continue to function as if made on the new location. However, to reduce confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line: diff --git a/content/rest/issues/sub-issues.md b/content/rest/issues/sub-issues.md index 07cce607c4ba..f7d9de205c0f 100644 --- a/content/rest/issues/sub-issues.md +++ b/content/rest/issues/sub-issues.md @@ -11,6 +11,4 @@ autogenerated: rest allowTitleToDifferFromFilename: true --- -{% data reusables.issues.release-stage %} - diff --git a/data/features/issue-types.yml b/data/features/issue-types.yml index 8cd17a8c69cb..4ab0d81619f8 100644 --- a/data/features/issue-types.yml +++ b/data/features/issue-types.yml @@ -2,4 +2,4 @@ versions: fpt: '*' ghec: '*' - ghes: '>=3.16' + ghes: '>=3.18' diff --git a/data/features/issues-advanced-search.yml b/data/features/issues-advanced-search.yml index 8378b523c618..fe3b59f64288 100644 --- a/data/features/issues-advanced-search.yml +++ b/data/features/issues-advanced-search.yml @@ -2,4 +2,4 @@ versions: fpt: '*' ghec: '*' - ghes: '>=3.16' + ghes: '>=3.18' diff --git a/data/features/sub-issues.yml b/data/features/sub-issues.yml index a4c0c0be6d77..38e21ad6c9de 100644 --- a/data/features/sub-issues.yml +++ b/data/features/sub-issues.yml @@ -2,4 +2,4 @@ versions: fpt: '*' ghec: '*' - ghes: '>=3.17' + ghes: '>=3.18' diff --git a/data/reusables/issues/release-stage.md b/data/reusables/issues/release-stage.md deleted file mode 100644 index 5a7769e0d432..000000000000 --- a/data/reusables/issues/release-stage.md +++ /dev/null @@ -1,3 +0,0 @@ ->[!NOTE] ->Issue types, sub-issues, and advanced issue search are currently in {% data variables.release-phases.public_preview %} for organizations. See the [GitHub Blog](https://github.blog/changelog/2025-01-13-evolving-github-issues-public-preview/). - diff --git a/data/reusables/pages/create-repo-name.md b/data/reusables/pages/create-repo-name.md index bab1d2e5a6b6..0ee1303c5cd7 100644 --- a/data/reusables/pages/create-repo-name.md +++ b/data/reusables/pages/create-repo-name.md @@ -1,3 +1,3 @@ 1. Type a name for your repository and an optional description. If you're creating a user or organization site, your repository must be named `.github.io` or `.github.io`. If your user or organization name contains uppercase letters, you must lowercase the letters. -For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites). +For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites). ![Screenshot of {% data variables.product.prodname_pages %} settings in a repository. The repository name field contains the text "octocat.github.io" and is outlined in dark orange.](/assets/images/help/pages/create-repository-name-pages.png) diff --git a/data/reusables/pages/default-domain-information.md b/data/reusables/pages/default-domain-information.md index 49ce6980ccc0..11d34cc91128 100644 --- a/data/reusables/pages/default-domain-information.md +++ b/data/reusables/pages/default-domain-information.md @@ -1 +1 @@ -For more information about the default domain for your site, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites). +For more information about the default domain for your site, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites). diff --git a/data/reusables/pages/emu-org-only.md b/data/reusables/pages/emu-org-only.md index 66be8fbabc73..31e201488150 100644 --- a/data/reusables/pages/emu-org-only.md +++ b/data/reusables/pages/emu-org-only.md @@ -1,6 +1,6 @@ {% ifversion ghec %} > [!NOTE] -> If you're a {% data variables.enterprise.prodname_managed_user %}, you can only publish {% data variables.product.prodname_pages %} sites from repositories owned by organizations. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users). +> If you're a {% data variables.enterprise.prodname_managed_user %}, you can only publish {% data variables.product.prodname_pages %} sites from repositories owned by organizations. For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/github-pages-limits#limits-for-enterprise-managed-users). {% endif %} diff --git a/src/events/components/experiments/experiments.ts b/src/events/components/experiments/experiments.ts index 859125bcd827..050d134e6936 100644 --- a/src/events/components/experiments/experiments.ts +++ b/src/events/components/experiments/experiments.ts @@ -29,7 +29,7 @@ export const EXPERIMENTS = { 'enterprise-cloud@latest', 'enterprise-server@latest', ], // Only enable for versions - alwaysShowForStaff: false, // When set to true, staff will always see the experiment (determined by the `staffonly` cookie) + alwaysShowForStaff: true, // When set to true, staff will always see the experiment (determined by the `staffonly` cookie) turnOnWithURLParam: 'ai_search', /// When the query param `?feature=ai_search` is set, the experiment will be enabled }, /* Add new experiments here, example: diff --git a/src/search/components/input/SearchOverlay.tsx b/src/search/components/input/SearchOverlay.tsx index ed8d0e2fa479..f8609b4b0b3a 100644 --- a/src/search/components/input/SearchOverlay.tsx +++ b/src/search/components/input/SearchOverlay.tsx @@ -335,6 +335,9 @@ export function SearchOverlay({ if (searchParams.has('search-overlay-input')) { searchParams.delete('search-overlay-input') } + if (searchParams.has('search-overlay-ask-ai')) { + searchParams.delete('search-overlay-ask-ai') + } router.push(`${selectedOption.url}?${searchParams.toString()}` || '') onClose() } @@ -376,8 +379,17 @@ export function SearchOverlay({ eventGroupId: askAIEventGroupId.current, }) setSelectedIndex(-1) - // hardcode the feature to ai_search for now, delete when GA is ready - window.open(`${url}?feature=ai_search` || '', '_blank') + const searchParams = new URLSearchParams((router.query as Record) || {}) + if (searchParams.has('search-overlay-open')) { + searchParams.delete('search-overlay-open') + } + if (searchParams.has('search-overlay-input')) { + searchParams.delete('search-overlay-input') + } + if (searchParams.has('search-overlay-ask-ai')) { + searchParams.delete('search-overlay-ask-ai') + } + window.open(`${url}?${searchParams.toString()}` || '', '_blank') } // Handle keyboard navigation of suggestions