-
Notifications
You must be signed in to change notification settings - Fork 34.9k
Closed
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalitygitGIT issuesGIT issuesgithubGithub extensionGithub extensiongithub-repositoriesIssues related to GitHub RepositoriesIssues related to GitHub Repositories
Milestone
Description
GitHub's remote response when pushing a branch already provides a shortcut to create a PR, and even warns about dependabot alerts, or even rejects pushing due to branch protection and secret scanning:
> git push -u origin digitarald/branchy
Create a pull request for 'digitarald/branchy' on GitHub by visiting:
https://github.com/…/pull/new/digitarald/branchy
GitHub found 153 vulnerabilities on …'s default branch (3 critical, 29 high, 118 moderate, 3 low). To find out more, visit:
https://github.com/…/security/dependabot
When users push with VS Code, this information is lost (or at least buried in git output).
Ideas (there might be other responses I am not aware of)
- Branch protection: GitHub - Handle GitHub's branch protection push errors #169779
- Secret scanning: Handle GitHub's Secret Scanning Push Protection #169355
- Create PR: Create a PR after pushing a remote branch #169776
- Security Alerts: Potential for a security extension.
lszomoru15MariamS and tsugabloom
Metadata
Metadata
Assignees
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalitygitGIT issuesGIT issuesgithubGithub extensionGithub extensiongithub-repositoriesIssues related to GitHub RepositoriesIssues related to GitHub Repositories