A site admin clears a restriction on repository creation in organizations in the enterprise. For more information, see "Enforcing repository management policies in your enterprise."{% if enterpriseServerVersions contains currentVersion %}
enterprise.config.lock_anonymous_git_access
A site admin locks anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. For more information, see "Enforcing repository management policies in your enterprise."
enterprise.config.unlock_anonymous_git_access
A site admin unlocks anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. For more information, see "Enforcing repository management policies in your enterprise."{% endif %}
Issues and pull requests
Name
Description
issue.update
An issue's body text (initial comment) changed.
issue_comment.update
A comment on an issue (other than the initial one) changed.
pull_request_review_comment.delete
A comment on a pull request was deleted.
issue.destroy
An issue was deleted from the repository. For more information, see "Deleting an issue."
Organizations
Name
Description
org.async_delete
A user initiated a background job to delete an organization.
org.delete
An organization was deleted by a user-initiated background job.{% if currentVersion != "github-ae@latest" %}
A site admin blocked force pushes. For more information, see [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository.
repo.create
A repository was created.
repo.destroy
A repository was deleted.
repo.remove_member
A collaborator was removed from a repository.
repo.rename
A repository was renamed.
repo.transfer
A user accepted a request to receive a transferred repository.
repo.transfer_start
A user sent a request to transfer a repository to another user or organization.
Anonymous Git read access is disabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
repo.config.enable_anonymous_git_access
Anonymous Git read access is enabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
repo.config.lock_anonymous_git_access
A repository's anonymous Git read access setting is locked, preventing repository administrators from changing (enabling or disabling) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
repo.config.unlock_anonymous_git_access
A repository's anonymous Git read access setting is unlocked, allowing repository administrators to change (enable or disable) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %}
Site admin tools
Name
Description
staff.disable_repo
A site admin disabled access to a repository and all of its forks.
staff.enable_repo
A site admin re-enabled access to a repository and all of its forks.
staff.fake_login
A site admin signed into {% data variables.product.product_name %} as another user.
staff.repo_unlock
A site admin unlocked (temporarily gained full access to) one of a user's private repositories.
staff.unlock
A site admin unlocked (temporarily gained full access to) all of a user's private repositories.
Teams
Name
Description
team.create
A user account or repository was added to a team.
team.delete
A user account or repository was removed from a team.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
team.demote_maintainer
A user was demoted from a team maintainer to a team member.{% endif %}
team.destroy
A team was deleted.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
team.promote_maintainer
A user was promoted from a team member to a team maintainer.{% endif %}
Users
Name
Description
user.add_email
An email address was added to a user account.
user.async_delete
An asynchronous job was started to destroy a user account, eventually triggering user.delete.{% if enterpriseServerVersions contains currentVersion %}
user.change_password
A user changed his or her password.{% endif %}
user.create
A new user account was created.
user.delete
A user account was destroyed by an asynchronous job.
user.demote
A site admin was demoted to an ordinary user account.
user.destroy
A user deleted his or her account, triggering user.async_delete.{% if enterpriseServerVersions contains currentVersion %}
user.failed_login
A user tried to sign in with an incorrect username, password, or two-factor authentication code.
user.forgot_password
A user requested a password reset via the sign-in page.{% endif %}
user.login
A user signed in.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
Press p or to see the previous file or,
n or to see the next file
Comments
Integrate AWS S3
Use S3 remote
Select bucket
Access key
Finish
Use AWS S3 as storage!
Browsing data directories saved to S3 is possible with DAGsHub. Let's configure
your repository to easily display your data in the context of any commit!
Specify your S3 bucket
Select Region
af-south-1 - Africa (Cape Town)
ap-northeast-1 - Asia Pacific (Tokyo)
ap-northeast-2 - Asia Pacific (Seoul)
ap-south-1 - Asia Pacific (Mumbai)
ap-southeast-1 - Asia Pacific (Singapore)
ap-southeast-2 - Asia Pacific (Sydney)
ca-central-1 - Canada (Central)
eu-central-1 - EU (Frankfurt)
eu-north-1 - EU (Stockholm)
eu-west-1 - EU (Ireland)
eu-west-2 - EU (London)
eu-west-3 - EU (Paris)
sa-east-1 - South America (São Paulo)
us-east-1 - US East (N. Virginia)
us-east-2 - US East (Ohio)
us-gov-east-1 - US Gov East 1
us-gov-west-1 - US Gov West 1
us-west-1 - US West (N. California)
us-west-2 - US West (Oregon)
Congratulations!
docs is now integrated with AWS S3!
Delete Storage Key
Are you sure you want to delete this access key?
No
Yes
Integrate Google Cloud Storage
Use Google Storage
Select bucket
Upload key
Finish
Use Google Cloud Storage!
Browsing data directories saved to Google Cloud Storage is possible with DAGsHub. Let's configure
your repository to easily display your data in the context of any commit!
Specify your Google Storage bucket
Congratulations!
docs is now integrated with Google Cloud Storage!
Delete Storage Key
Are you sure you want to delete this access key?
No
Yes
Integrate Azure Cloud Storage
Use Azure Storage
Select bucket
Set key
Finish
Use Azure Cloud Storage!
Browsing data directories saved to Azure Cloud Storage is possible with DAGsHub. Let's configure
your repository to easily display your data in the context of any commit!
Specify your Azure Storage bucket
Congratulations!
docs is now integrated with Azure Cloud Storage!
Delete Storage Key
Are you sure you want to delete this access key?
No
Yes
Integrate S3 compatible storage
Use S3 like remote
Select bucket
Access key
Finish
Use any S3 compatible storage!
Browsing data directories saved to S3 compatible storage is possible with DAGsHub. Let's configure
your repository to easily display your data in the context of any commit!
Specify your S3 bucket
Bucket name cannot be the same as the repository name. Please change one of them.
Check this box only if you trust this domain, otherwise your data and credentials might be
stolen by man in the middle or spoofing attacks.
Congratulations!
docs is now integrated with your S3 compatible storage!