GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • GitHub Docs
  • Security and code quality
  • GitHub security features
  • Secure repository quickstart
  • Secret leakage risks
  • Secret scanning
  • Public monitoring
  • Push protection
  • Secret security with GitHub
  • Secret scanning alerts
  • Custom patterns
  • Validity checks
  • Delegated bypass
  • Bypass requests

This view

  • Original page
  • New address

GeezerVison is showing docs.github.com — Tutorials for security and code quality - GitHub Docs

Tutorials for security and code quality

Build skills and knowledge about GitHub's security and code quality features through examples and hands-on activities.

  • Secure your secrets at scale with GitHub, 1 of 12
  • Improve code quality at scale with GitHub, 2 of 12
  • Trialing GitHub Advanced Security, 3 of 12
    • Planning a trial of GitHub Advanced Security, 1 of 5
    • Setting up a trial of GitHub Advanced Security, 2 of 5
    • Enabling security features in your trial, 3 of 5
    • Exploring your enterprise trial of GitHub Secret Protection, 4 of 5
    • Exploring your enterprise trial of GitHub Code Security, 5 of 5
  • Securing your organization, 4 of 12
    • Best practices for preventing data leaks in your organization, 1 of 9
    • Running a security campaign to fix alerts at scale, 2 of 9
    • Prioritizing Dependabot and code scanning alerts using production context, 3 of 9
    • Interpreting secret risk assessment results, 4 of 9
    • Interpreting code security risk assessment results, 5 of 9
    • Organizing remediation efforts for leaked secrets, 6 of 9
    • Protecting against security threats, 7 of 9
    • Preparing for a security incident, 8 of 9
    • Responding to a security incident, 9 of 9
  • Remediate leaked secrets, 5 of 12
    • Calculating the cost savings of push protection, 1 of 4
    • Assessing the impact of GitHub Secret Protection, 2 of 4
    • Evaluating alerts from secret scanning, 3 of 4
    • Remediating a leaked secret in your repository, 4 of 4
  • Secret scanning partner program, 6 of 12
  • Customize code scanning, 7 of 12
    • Evaluating default setup for code scanning, 1 of 8
    • Preparing your code for CodeQL analysis, 2 of 8
    • Analyzing your code with CodeQL queries, 3 of 8
    • Uploading CodeQL analysis results to GitHub, 4 of 8
    • Running CodeQL code scanning in a container, 5 of 8
    • Customizing analysis with CodeQL packs, 6 of 8
    • Creating CodeQL query suites, 7 of 8
    • Creating and working with CodeQL packs, 8 of 8
  • Secure your dependencies, 8 of 12
    • Dependabot quickstart guide, 1 of 6
    • Automating Dependabot with GitHub Actions, 2 of 6
    • Optimizing the creation of pull requests for Dependabot version updates, 3 of 6
    • Setting up Dependabot to run on self-hosted action runners using the Actions Runner Controller, 4 of 6
    • Customizing Dependabot pull requests to fit your processes, 5 of 6
    • Customizing your dependency review action configuration, 6 of 6
  • Implement supply chain best practices, 9 of 12
    • Securing your end-to-end supply chain, 1 of 4
    • Best practices for securing accounts, 2 of 4
    • Best practices for securing code in your supply chain, 3 of 4
    • Best practices for securing your build system, 4 of 4
  • Manage security alerts, 10 of 12
    • Prioritizing Dependabot alerts using metrics, 1 of 2
    • Participating in a code security campaign, 2 of 2
  • Improving the quality of your code, 11 of 12
    • Preventing code quality issues from reaching your default branch, 1 of 2
    • Raising your repository's code quality score, 2 of 2
  • Fixing reported vulnerabilities, 12 of 12
    • Collaborating in a temporary private fork to resolve a repository security vulnerability, 1 of 2
    • Best practices for writing repository security advisories, 2 of 2
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.