AZ-400 Question 288
Single answerYou maintain a private GitHub repository for a team project. You want to monitor commit frequency, pull request activity, and issue trends. In addition, you need to create and configure charts to visualize these metrics for your team. Which action must you take to ensure your team can view and customize these insights within the repository?
- A
Enable GitHub Insights in the repository� settings and access the Insights tab to create and configure charts
- B
Create a separate .github-insights.yml file in your repository with chart definitions and push the file to the main branch
- C
Enable GitHub Actions and add a workflow that automates chart generation via scheduled runs
- D
Grant public access to the repository so that the Insights tab becomes visible to everyone
Show answer and explanation
Correct answer: A
Explanation
GitHub provides built-in repository Insights that include data on commits, issues, pull requests, and more. For a private repository, ensuring that the repository settings allow team members to see Insights is essential. From the Insights tab, you can view default charts like traffic and clone count, as well as details about commits and code frequency. Refer to GitHub� documentation on 'Viewing repository insights' for more information.
- A. Correct.
Correct. In GitHub, repository insights are accessed from the Insights tab. You must have the appropriate permissions to view or configure these insights, and enabling them in the repository settings ensures your team can monitor commit frequency, pull requests, issues, and create custom charts.
- B. Incorrect.
Incorrect. While a .github folder is commonly used for workflows and configuration files, there's no official .github-insights.yml file to enable or configure GitHub insights. This distractor might seem plausible because GitHub often uses YAML workflows, but it's not the correct solution for enabling Insights.
- C. Incorrect.
Incorrect. GitHub Actions can automate tasks, but it is not required to enable or configure built-in GitHub Insights charts. Actions may help generate additional reports, but they do not replace the native Insights functionality.
- D. Incorrect.
Incorrect. Making the entire repository public simply allows general public access. Within private repositories, authorized team members can view Insights without making the repository publicly accessible.