GitHub AE release notes

December 6, 2021

GitHub began rolling these changes out to enterprises on December 6, 2021.

    Administração

  • Customers with active or trial subscriptions for GitHub AE can now provision GitHub AE resources from the Azure Portal. Your Azure subscription must be feature-flagged to access GitHub AE resources in the portal. Contact your account manager or Equipe de Vendas do GitHub to validate your Azure subscription's eligibility. For more information, see "Setting up a trial of GitHub AE."

  • GitHub Actions

  • GitHub Actions is now generally available for GitHub AE. GitHub Actions is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "Introduction to GitHub Actions."

  • Self-hosted runners are the default type of runner system on GitHub AE, and are now generally available for GitHub Actions. With self-hosted runners, you can manage your own machines or containers for the execution of GitHub Actions jobs. For more information, see "About self-hosted runners" and "Adding self-hosted runners."

  • Environments, environment protection rules, and environment secrets are now generally available for GitHub Actions on GitHub AE. For more information, see "Environments."

  • GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can achieve the following.

    • View and understand complex workflows.
    • Track progress of workflows in real-time.
    • Troubleshoot runs quickly by easily accessing logs and jobs metadata.
    • Monitor progress of deployment jobs and easily access deployment targets.

    For more information, see "Using the visualization graph."

  • GitHub Actions now lets you control the permissions granted to the GITHUB_TOKEN secret. The GITHUB_TOKEN is an automatically generated secret that lets you make authenticated calls to the API for GitHub AE in your workflow runs. GitHub Actions generates a new token for each job and expires the token when a job completes. The token has write permissions to a number of API endpoints except in the case of pull requests from forks, which are always read. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "Authentication in a workflow."

  • O GitHub Actions agora é compatível com fluxos de trabalho push e pull_request, que procuram algumas palavras-chave comuns na sua mensagem de commit.

  • GitHub CLI 1.9 and later allows you to work with GitHub Actions in your terminal. For more information, see GitHub Blog.

  • Varredura de código

  • Code scanning is now in beta for GitHub AE. For more information, see "About code scanning."

  • Varredura secreta

  • You can now specify your own patterns for secret scanning with the beta of custom patterns on GitHub AE. You can specify patterns for repositories, organizations, and your entire enterprise. When you specify a new pattern, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. For more information, see "Defining custom patterns for secret scanning."

  • GitHub Connect

  • GitHub Connect is now available in beta for GitHub AE. GitHub Connect brings the power of the world's largest open source community to your enterprise. You can allow users to view search results from GitHub.com on GitHub AE, show contribution counts from GitHub AE on GitHub.com, and use GitHub Actions from GitHub.com. For more information, see "Managing connections between your enterprise accounts."

  • GitHub Package Registry

  • You can now delete any package or package version for GitHub Packages from GitHub AE's web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "Deleting and restoring a package."

  • The npm registry for GitHub Packages and GitHub.com no longer returns a time value in metadata responses, providing substantial performance improvements. GitHub will continue returning the time value in the future.

  • Gerar logs de auditoria

  • Events for pull requests and pull request reviews are now included in the audit log for both enterprises and organizations. These events help administrators better monitor pull request activity and ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events.

  • Additional events for GitHub Actions are now included in the audit log for both enterprises and organizations.

    • A workflow is deleted or re-run.
    • A self-hosted runner's version is updated.
  • Autenticação

  • GitHub AE now officially supports Okta for SAML single sign-on (SSO) and user provisioning with SCIM. You can also map groups in Okta to teams on GitHub AE. For more information, see "Configuring authentication and provisioning for your enterprise using Okta" and "Mapping Okta groups to teams."

  • The format of authentication tokens for GitHub AE has changed. The change affects the format of personal access tokens and access tokens for OAuth Apps, as well as user-to-server, server-to-server, and refresh tokens for GitHub Apps. GitHub recommends updating existing tokens as soon as possible to improve security and allow secret scanning to detect the tokens. For more information, see "About authentication to GitHub" and "About secret scanning."

  • You can now authenticate SSH connections to GitHub AE using a FIDO2 security key by adding an sk-ecdsa-sha2-nistp256@openssh.com SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. Storing the key on separate hardware and requiring physical interaction for your SSH key offers additional security. Since the key is stored on hardware and is non-extractable, the key can't be read or stolen by software running on the computer. The physical interaction prevents unauthorized use of the key since the security key will not operate until you physically interact with it. For more information, see "Generating a new SSH key and adding it to the ssh-agent."

  • Git Credential Manager (GCM) Core versions 2.0.452 and later now provide secure credential storage and multi-factor authentication support for GitHub AE. GCM Core with support for GitHub AE is included with Git for Windows versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the latest release and installation instructions in the microsoft/Git-Credential-Manager-Core repository.

  • Notificações

  • You can now configure which events you would like to be notified about on GitHub AE. From any repository, select the Watch drop-down, then click Custom. For more information, see "Configuring notifications."

  • Problemas e pull requests

  • With the latest version of Octicons, the states of issues and pull requests are now more visually distinct so you can scan status more easily. For more information, see GitHub Blog.

  • You can now see all pull request review comments in the Files tab for a pull request by selecting the Conversations drop-down. You can also require that all pull request review comments are resolved before anyone merges the pull request. For more information, see "About pull request reviews" and "About protected branches." For more information about management of branch protection settings with the API, see "Branches" in the REST API documentation and "Mutations" in the GraphQL API documentation.

  • You can now upload video files everywhere you write Markdown on GitHub AE. Share demos, show reproduction steps, and more in issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "Attaching files."

  • GitHub AE now shows a confirmation dialog when you request a review from a team with more than 100 members, allowing you to prevent unnecessary notifications for large teams.

  • When an issue or pull request has fewer than 30 possible assignees, the assignees control will list all potential users rather than a limited set of suggestions. This behavior helps people in small organizations to quickly find the right user. For more information about assigning users to issues and pull requests, see "Assigning issues and pull requests to other GitHub users."

  • You can now include multiple words after the # in a comment for an issue or pull request to further narrow your search. To dismiss the suggestions, press Esc.

  • To prevent the merge of unexpected changes after you enable auto-merge for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, GitHub AE will disable auto-merge for the pull request if the update causes a merge conflict. For more information about auto-merge, see "Automatically merging a pull request."

  • People with maintain access can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin access could manage this setting. Additionally, this setting can now by controlled using the "Create a repository" and "Update a repository" REST APIs. For more information, see "Managing auto-merge for pull requests in your repository."

  • The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name.

  • Repositórios

  • When viewing the commit history for a file, you can now click to view the file at the specified time in the repository's history.

  • You can now use the web UI to synchronize an out-of-date branch for a fork with the fork's upstream branch. If there are no merge conflicts between the branches, GitHub AE updates your branch either by fast-forwarding or by merging from upstream. If there are conflicts, GitHub AE will prompt you to open pull request to resolve the conflicts. For more information, see "Syncing a fork."

  • You can now sort the repositories on a user or organization profile by star count.

  • The Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another, now supports pagination. The API can also now return the results for comparisons over 250 commits. For more information, see the "Commits" REST API documentation and "Traversing with pagination."

  • When you define a submodule in your enterprise with a relative path, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. Relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY are supported. For more information about working with submodules, see Working with submodules on GitHub Blog.

  • By precomputing checksums, the amount of time a repository is under lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance.

  • Versões

  • You can now react with emoji to all releases on GitHub AE. For more information, see "About releases."

  • Temas

  • Dark and dark dimmed themes are now available for the web UI. GitHub AE will match your system preferences when you haven't set theme preferences in GitHub AE. You can also customize the themes that are active during day and night. For more information, see "Managing your theme settings."

  • markdown

  • Markdown files in your repositories now automatically generate a table of contents in the header the file has two or more headings. The table of contents is interactive and links to the corresponding section. All six Markdown heading levels are supported. For more information, see "About READMEs."

  • code markup is now supported in titles for issues and pull requests. Text within backticks (`) will appear rendered in a fixed-width font anywhere the issue or pull request title appears in the web UI for GitHub AE.

  • While editing Markdown in files, issues, pull requests, or comments, you can now use a keyboard shortcut to insert a code block. The keyboard shortcut is command + E on a Mac or Ctrl + E on other devices. For more information, see "Basic writing and formatting syntax."

  • You can append ?plain=1 to the URL for any Markdown file to display the file without rendering and with line numbers. You can use the plain view to link other users to specific lines. For example, appending ?plain=1#L52 will highlight line 52 of a plain text Markdown file. For more information, "Creating a permanent link to a code snippet."

  • Aplicativos do GitHub

  • API requests to create an installation access token now respect IP allow lists for an enterprise or organization. Any API requests made with an installation access token for a GitHub App installed on your organization already respect IP allow lists. This feature does not currently consider any Azure network security group (NSG) rules that GitHub Support has configured for your enterprise. For more information, see "Restricting network traffic to your enterprise," "Managing allowed IP addresses for your organization," and "Apps" in the REST API documentation.

  • Webhooks

  • You can now programmatically resend or check the status of webhooks through the REST API. For more information, see "Repositories," "Organizations," and "Apps" in the REST API documentation.

Semana de 3 de março de 2021

GitHub began rolling these changes out to enterprises on 3 de março de 2021.

    GitHub Actions beta

  • GitHub Actions is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "Introduction to GitHub Actions."

    Please note that when GitHub Actions is enabled during this upgrade, two organizations named "GitHub Actions" (@actions and @github) will appear in your enterprise. These organizations are required by GitHub Actions. Users named @ghost and @actions appear as the actors for creation of these organizations in the audit log.

  • GitHub Packages beta

  • GitHub Package Registry é um serviço de hospedagem de pacotes, integrado nativamente a GitHub Actions, APIs e webhooks. Crie um fluxo de trabalho DevOps de ponta a ponta que inclui seu código, integração contínua e soluções de implantação. Durante este beta, GitHub Package Registry é oferecido gratuitamente para clientes de GitHub AE.

  • Segurança Avançada do GitHub beta

  • Segurança Avançada GitHub está disponível na versão beta e inclui tanto a verificação de código quanto a digitalização de segredo. Durante este beta, as funcionalidades de Segurança Avançada GitHub são oferecidas gratuitamente para clientes de GitHub AE. Os administradores do repositório e da organização podem optar por usar Segurança Avançada GitHub na aba Segurança e Análise nas configurações.

    Saiba mais sobre Segurança Avançada GitHub digitalização de código e scanning secreto em GitHub AE.

  • Gerenciar equipes do seu provedor de identidade (IdP)

  • Agora os clientes que usam SCIM (Sistema para Gerenciamento de Identidade entre Domínios) podem sincronizar grupos de segurança no diretório ativo do Azure com equipes de GitHub. Uma vez que uma equipe tenha sido vinculada a um grupo de segurança, a associação será atualizada automaticamente em GitHub AE quando um usuário for adicionado ou removido do seu grupo de segurança atribuído.

  • Beta de listas de permissões de IP

  • As Listas de endereços de IP permitidos de GitHub fornecem a capacidade de filtrar tráfego a partir de intervalos IP especificados pelo administrador, definidos pela notação CIDR. A lista de permissão é definida no nível de conta corporativa ou de organização em Segurança > Configurações. Todo o tráfego que tenta alcançar recursos dentro da conta corporativa e organizações são filtradas pela lista de endereços de IP permitidos. Essa funcionalidade é fornecida em adição à capacidade de solicitar alterações de grupo de segurança de rede que filtram todo o tráfego do inquilino GHAE.

    Alterações de desenvolvedor

  • Os proprietários da organização podem agora desabilitar a publicação dos sites de GitHub Pages a partir de repositórios na organização. Isso não cancelará a publicação dos sites existentes.

  • Os repositórios que usam GitHub Pages agora podem ser criados e implantados a partir de qualquer branch.

  • Ao escrever um problema ou pull request, a sintaxe da lista para itens, números e tarefas agora será concluída automaticamente depois que você pressionar return ou enter.

  • Agora, você pode excluir um diretório em um repositório da página do repositório. Ao acessar um diretório, um novo botão kebab ao lado do botão "Adicionar arquivo" dá a opção de excluir o diretório.

  • Agora é mais fácil e rápido fazer referência a problemas ou pull requests, com a busca em várias palavras após o "#".

  • Mudanças na administração

  • Os proprietários da empresa podem agora publicar uma mensagem obrigatória. A mensagem é mostrada a todos os usuários e devem reconhecê-la. Isto pode ser utilizado para exibir informações importantes, termos de serviço ou políticas.

  • A permissão de caminho único de aplicativo GitHub agora pode oferecer suporte para até dez arquivos.

  • Ao configurar um aplicativo GitHub, a URL de retorno de chamada de autorização é um campo obrigatório. Agora, permitiremos que o integrador especifique várias URLs de retorno de chamada. GitHub AE nega a autorização se a URL de retorno de chamada da requisição não estiver listada.

  • Um novo ponto de extremidade da API permite a troca de um usuário para um token de servidor para um token de servidor com escopo definido para repositórios específicos.

  • Agora, os eventos são registrados no log de auditoria em promovendo um integrante da equipe para ser um mantenedor de equipe e ao rebaixar um mantenedor da equipe para ser um integrante da equipe.

  • O fluxo de autorização do dispositivo OAuth agora é compatível. Isso permite que qualquer cliente CLI ou ferramenta de desenvolvedor efetue a autenticação usando um sistema secundário.

  • Um usuário não pode mais excluir sua conta se o provisionamento de SCIM estiver habilitado.

  • Renomeação do branch padrão

  • Os proprietários de empresas e organizações agora podem definir o nome do branch padrão para novos repositórios. Os proprietários de empresas também podem aplicar sua escolha do nome padrão do branch em todas as organizações ou permitir que as organizações individuais escolham os seus próprios.

    Os repositórios existentes não são afetados por essas configurações, e seu nome de branch padrão não será alterado.

    Esta alteração é uma das muitas alterações que GitHub está fazendo para ser compatível com projetos e mantenedores que desejam renomear seu branch padrão. Para saber mais, consulte github/renaming.

    Correções de erros

  • Os usuários não podem mais definir um endereço de e-mail de backup no perfil deles. O endereço de e-mail deles é definido apenas por meio do IdP.

  • Você não pode mais habilitar a autenticação de dois fatores após a configuração de autenticação através do seu IdP.

  • GitHub AE agora pode conectar-se ao Azure Boards.

  • Os cabeçalhos de versão estavam ausentes nas APIs e agora foram definidos como "GitHub AE".

  • Foram corrigidos links na documentação.

  • Ocorreu uma falha na configuração de encaminhamento de log de auditoria nas configurações da empresa.

  • Acesar os gists pode gerar um "500 error".

  • O e-mail de suporte ou URL não foi salvo. Agora, será salvo após alguns minutos.

  • Os modelos de pull request no nível de organização não estavam sendo aplicados em todos os pull requests na organização.

    Problemas conhecidos

  • Os dados de localização geográfica não são mostrados no log de auditoria. As informações de localização podem ser detectadas de outra forma no endereço IP associado a cada evento.

  • O link para GitHub Package Registry de uma página do repositório mostra uma página de pesquisa incorreta quando esse repositório não tem pacotes.

Esse documento ajudou você?

Política de Privacidade

Ajude-nos a tornar esses documentos ótimos!

Todos os documentos do GitHub são de código aberto. Você percebeu que algo que está errado ou não está claro? Envie um pull request.

Faça uma contribuição

Ou, aprenda como contribuir.