Octomerger Bot
@@ -110,7 +110,7 @@ Once this is initialized, you can reconfigure any settings after the initializat
|
||||
|
||||
1. To the right of "Configure email settings", click **Configure**.
|
||||
|
||||
2. Select **Enable email**. This will enable both outbound and inbound email, however, for inbound email to work you will also need to configure your DNS settings. For more information, see "[AUTOTITLE](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
|
||||
2. Select **Enable email**. This will enable both outbound and inbound email, however, for inbound email to work you will also need to configure your DNS settings. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
|
||||
|
||||
3. Complete your email server settings:
|
||||
- In the **Server address** field, type the address of your SMTP server.
|
||||
|
||||
@@ -22,7 +22,7 @@ You can choose which package ecosystems you'd like to enable, disable, or set to
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before you can configure individual package ecosystems, {% data variables.product.prodname_registry %} must be enabled and configured for your instance. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
|
||||
Before you can configure individual package ecosystems, {% data variables.product.prodname_registry %} must be enabled and configured for your instance. For more information, see "[AUTOTITLE](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
|
||||
|
||||
## Enabling or disabling individual package ecosystems
|
||||
|
||||
|
||||
@@ -25,18 +25,18 @@ topics:
|
||||
|
||||
If you plan to enable {% data variables.product.prodname_container_registry %} for the users of your instance, at least 10% more CPU resources are required.
|
||||
|
||||
We recommend reviewing the levels of activity for users and automations on the instance to ensure that you have provisioned adequate CPU for your users. For more information, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)."
|
||||
We recommend reviewing the levels of activity for users and automations on the instance to ensure that you have provisioned adequate CPU for your users. For more information, see "[AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance)."
|
||||
|
||||
For more information about minimum hardware requirements for {% data variables.location.product_location %}, see the hardware considerations for your instance's platform.
|
||||
|
||||
- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
|
||||
- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
|
||||
- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
|
||||
- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
|
||||
- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
|
||||
- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
|
||||
- [AWS](/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws#hardware-considerations)
|
||||
- [Azure](/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure#hardware-considerations)
|
||||
- [Google Cloud Platform](/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
|
||||
- [Hyper-V](/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
|
||||
- [OpenStack KVM](/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
|
||||
- [VMware](/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware#hardware-considerations)
|
||||
|
||||
For more information about adjusting resources for an existing instance, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)."
|
||||
For more information about adjusting resources for an existing instance, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources)."
|
||||
|
||||
## Step 3: Enable {% data variables.product.prodname_registry %} and configure external storage
|
||||
|
||||
|
||||
@@ -46,7 +46,7 @@ There are five main archetypes for organizational structure. The archetypes are
|
||||
- Whether to use a single organization or multiple organizations
|
||||
- Whether to grant all members access to all repositories, or use teams to manage repository access more granularly
|
||||
|
||||
For more information about teams, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
|
||||
For more information about teams, see "[AUTOTITLE](/organizations/organizing-members-into-teams/about-teams)."
|
||||
|
||||
### Single organization with direct repository access
|
||||
|
||||
@@ -54,7 +54,7 @@ The simplest organizational structure is a single organization, where members ar
|
||||
|
||||
This structure works best for small companies, such as startups, where everyone collaborates on everything. It can work for medium-sized companies as well, if trust is high.
|
||||
|
||||
To use this archetype, set the base permissions for the organization to "Write" or "Read." For more information, see "[Setting base permissions for an organization](/organizations/managing-user-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)."
|
||||
To use this archetype, set the base permissions for the organization to "Write" or "Read." For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)."
|
||||
|
||||
### Single organization with teams for repository access
|
||||
|
||||
@@ -87,4 +87,4 @@ Then, create a second organization specifically for more sensitive repositories.
|
||||
## Further reading
|
||||
|
||||
- [Organize your experts with ad hoc teams](https://github.blog/2017-02-15-organize-your-experts-with-ad-hoc-teams/) in the {% data variables.product.company_short %} blog
|
||||
- "[Best practices for organizations](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)"
|
||||
- "[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Persisting environment variables and temporary files
|
||||
intro: 'You can configure custom environment variables so that they are set to the same value every time you open a codespace. You can also ensure that temporary files are not deleted when a codespace stops.'
|
||||
intro: You can configure custom environment variables so that they are set to the same value every time you open a codespace. You can also ensure that temporary files are not deleted when a codespace stops.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -48,7 +48,7 @@ Only use this method for values that you are happy to commit to your repository
|
||||
|
||||
The environment variable will be set within your editor's remote server process, and will be available for sub-processes of that remote server process, such as terminals and debugging sessions. However, the variable will not be available more broadly inside the container. This method is useful if you don't need the environment variable to be set for other background processes that run at startup, and if you are using a premade image and don't have or want a custom Dockerfile.
|
||||
|
||||
This setting will take effect when you rebuild your container or create a new codespace after pushing this change to the repository. For more information about applying configuration changes to a codespace, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
|
||||
This setting will take effect when you rebuild your container or create a new codespace after pushing this change to the repository. For more information about applying configuration changes to a codespace, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
|
||||
|
||||
#### Use a custom Dockerfile
|
||||
|
||||
@@ -56,11 +56,11 @@ If you are using a custom Dockerfile you can set the environment variable there
|
||||
|
||||
This method is useful if you already have a Dockerfile and want to set a variable on a container-wide level.
|
||||
|
||||
This setting will take effect when you rebuild your container or create a new codespace after pushing this change to the repository. For more information about applying configuration changes to a codespace, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
|
||||
This setting will take effect when you rebuild your container or create a new codespace after pushing this change to the repository. For more information about applying configuration changes to a codespace, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
|
||||
|
||||
#### Use encrypted secrets
|
||||
|
||||
You can use encrypted secrets for {% data variables.product.prodname_github_codespaces %} to set custom variables for codespaces created for the repository. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
|
||||
You can use encrypted secrets for {% data variables.product.prodname_github_codespaces %} to set custom variables for codespaces created for the repository. For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
|
||||
|
||||
You should use this method for environment variable values that you do not want to commit to the repository as plaintext.
|
||||
|
||||
@@ -68,10 +68,10 @@ This setting will take effect the next time you create a codespace for this repo
|
||||
|
||||
### For all codespaces that you create
|
||||
|
||||
If you want to set a personalized environment variable for all codespaces that you create you can set this using a file in your `dotfiles` repository. For example, add `VARNAME=value` in the `.bash_profile` file. Environment variables you set in a dotfile are personal to you and are not set for anyone else. For more information about Dotfiles, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#dotfiles)."
|
||||
If you want to set a personalized environment variable for all codespaces that you create you can set this using a file in your `dotfiles` repository. For example, add `VARNAME=value` in the `.bash_profile` file. Environment variables you set in a dotfile are personal to you and are not set for anyone else. For more information about Dotfiles, see "[AUTOTITLE](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#dotfiles)."
|
||||
|
||||
## Preventing temporary files from being automatically deleted
|
||||
|
||||
Files saved to your workspace will be available the next time you start the codespace. The exception to this is any file you save in the `/tmp` directory. The contents of this directory are deleted each time the codespace stops (for example, when the codespace session times out after a period of inactivity).
|
||||
|
||||
If you have temporary files that you want to be available the next time you start the codespace, do not save them in the `/tmp` directory. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
|
||||
If you have temporary files that you want to be available the next time you start the codespace, do not save them in the `/tmp` directory. For more information, see "[AUTOTITLE](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
|
||||
|
||||
@@ -56,7 +56,7 @@ Before you require use of two-factor authentication, we recommend notifying {% i
|
||||
|
||||
## Viewing people who were removed from your organization
|
||||
|
||||
To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can search your organization's audit log for people removed from your organization. The audit log event will show if a person was removed for 2FA non-compliance. For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
|
||||
To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can search your organization's audit log for people removed from your organization. The audit log event will show if a person was removed for 2FA non-compliance. For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
|
||||
@@ -25,7 +25,7 @@ When you view a forked repository on {% data variables.product.product_name %},
|
||||
|
||||
In open source projects, forks are often used to iterate on ideas or changes before incorporating the changes into the upstream repository. {% data reusables.repositories.about-giving-access-to-forks %}
|
||||
|
||||
Deleting a fork will not delete the original upstream repository. You can make any changes you want to your fork, and there will be no effect on the upstream. For example, you can add collaborators, rename files, or generate {% data variables.product.prodname_pages %} on the fork without affecting the upstream. {% ifversion fpt or ghec %} After a fork is deleted, you cannot restore the fork. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} If you delete a private repository, all forks of the repository are deleted.
|
||||
Deleting a fork will not delete the original upstream repository. You can make any changes you want to your fork, and there will be no effect on the upstream. For example, you can add collaborators, rename files, or generate {% data variables.product.prodname_pages %} on the fork without affecting the upstream. {% ifversion fpt or ghec %} After a fork is deleted, you cannot restore the fork. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/restoring-a-deleted-repository)."{% endif %} If you delete a private repository, all forks of the repository are deleted.
|
||||
|
||||
## About creating forks
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About permissions and visibility of forks
|
||||
shortTitle: Permissions and visibility
|
||||
intro: The permissions and visibility of forks depend on whether the upstream repository is public or private, {% ifversion fpt %}and whether it is owned by an organization{% else %}whether it is owned by an organization, and the policies of your enterprise{% endif %}.
|
||||
intro: 'The permissions and visibility of forks depend on whether the upstream repository is public or private, {% ifversion fpt %}and whether it is owned by an organization{% else %}whether it is owned by an organization, and the policies of your enterprise{% endif %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -17,7 +17,7 @@ topics:
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% ifversion ghec %}{% data reusables.enterprise-accounts.emu-forks %}{% endif %} For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% ifversion ghec %}{% data reusables.enterprise-accounts.emu-forks %}{% endif %} For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -54,4 +54,4 @@ Forks within the same organization copy the collaborators and team settings of t
|
||||
- That organization controls the permissions of its forks.
|
||||
- Any teams from the upstream permission structure that exist and are visible in the target organization or user namespace will have their permissions copied.
|
||||
- Admin permissions remain with the upstream owner, except when a user forks into a different organization.
|
||||
- If that repository is forked to a user namespace, the organization maintains admin permissions and any teams with access maintain access.
|
||||
- If that repository is forked to a user namespace, the organization maintains admin permissions and any teams with access maintain access.
|
||||
|
||||
Reference in New Issue
Block a user