Test legat de ghid · Mediu Nivel

Test de revizuire a codului AI

Review PR context, GitHub Actions, file exclusions, balanced review settings, and the distinction between comments and approvals.

Căi de ghidare aferenteRevizuirea codului AI
Întrebare 1 de 8

Ce analizează de obicei un instrument de examinare a codului AI?

Previzualizează fiecare întrebare8 întrebări

Răspunsurile și explicațiile apar pe măsură ce susțineți testul.

  1. Ce analizează de obicei un instrument de examinare a codului AI?
    • O diferență de solicitare de extragere plus un context de depozit relevant
    • Registrele de salarizare ale unei companii
    • Calendarul dezvoltatorului
    • Copie de marketing
  2. De ce instrumentele de revizuire AI preiau fișierele conexe dincolo de liniile modificate?
    • Pentru a încetini revizuirea
    • Deoarece corectitudinea unei modificări depinde adesea de codul pe care nu îl atinge
    • Pentru că diferențele sunt întotdeauna goale
    • Pentru a șterge fișierele neutilizate
  3. How should a team treat AI code-review comments?
    • As confirmed defects that must all be applied
    • As a reason to merge automatically
    • As suggestions to verify against code, tests, and project requirements
    • As a replacement for security review
  4. What does GitHub say powers Copilot’s agentic code-review capabilities?
    • A browser-only linter
    • A mandatory local database
    • An external CI service required for all repositories
    • GitHub Actions
  5. What is GitHub Copilot code review’s default review type?
    • A comment review that does not count as an approval
    • An automatic approval
    • An automatic merge
    • A mandatory request-changes review
  6. What can GitHub content-exclusion settings do for Copilot review?
    • Delete those files from the repository
    • Prevent selected files or directories from being used as review context
    • Guarantee no model errors
    • Publish excluded source code
  7. What is GitHub Copilot code review’s “Balanced” effort level described to provide?
    • A guaranteed correct approval
    • Only formatting feedback
    • Deeper analysis of complex logic, security-sensitive code, and cross-service changes
    • A production deployment
  8. When can a Copilot code-review assessment satisfy merge requirements?
    • Whenever the assessment reports no issues
    • Whenever a pull request includes AI-generated comments
    • By default, even if branch protection requires human approval
    • Only when the repository separately enables an approving review; an assessment alone does not count