270 Resultados de la búsqueda para "pull requests"

security vulnerability in a dependency. Enforce dependency reviews on your pull requests. Assess the impact of that vulnerability on your code and decide what

cambios List pull requests Create a pull request Get a pull request Update a pull request List commits on a pull request List pull requests files Check

repositories Create, close, edit, and view issues and pull requests Review, diff, and merge pull requests Run, view, and list workflows Create, list, view,

actions for vulnerabilities in new or updated workflows When you open pull requests to update your workflows, it is good practice to use dependency review

my-feature branch. This ruleset requires signed commits, and three reviews on pull requests before they can be merged. An existing branch protection rule for the

will show any unassigned items. no:reviewers no:reviewers will show pull requests that do not have a reviewer. no:FIELD no:priority will show items with

use these components. Vulnerability data for these dependencies. For pull requests that contain changes to package manifests or lock files, you can display

automatically suggest fixes for any pull requests that are already open. The suggestions will only be generated for any pull requests that are opened after Copilot

a repository You can use the REST API to list comments on issues and pull requests for a repository. Every pull request is an issue, but not every issue

known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. For more information