Github Foundations · Free Practice Question Easy

Question 14

John would like to invite a new team member to collaborate on his project. How can John invite a user to his GitHub repository?

  • A

    access the repository settings on GitHub

  • B

    send an invitation via email

  • C

    create a separate repository for each collaborator

  • D

    share a link to the code repository

Reveal correct answer

Correct answer: A

Explanation

You can manage collaborators by accessing the repository settings on GitHub. This allows you to add or remove collaborators, define their permissions, and control access to the repository.

****************

WRONG ANSWERS:

  • While you can add collaborators, invitations are usually sent through GitHub, not via email. GitHub provides a user interface for adding collaborators in the repository settings.

  • Managing collaborators does not require creating separate repositories for each collaborator. Collaborator permissions are set at the repository level.

  • Sharing a link to the code repository is not a correct method for inviting collaborators on GitHub because simply sharing the link does not grant the necessary access or permissions for someone to collaborate effectively.

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository

A. To invite a new team member to collaborate on a GitHub repository, John should access the repository settings on GitHub. From there, he can navigate to the "Collaborators" section and add the user by entering their GitHub username or email address. This process ensures that the user is granted the appropriate access and permissions to contribute to the project.

B. Sending an invitation via email is not the correct method to invite a user to collaborate on a GitHub repository. While email notifications may be sent to the user after they have been added as a collaborator, the initial invitation and setup should be done directly within the repository settings on GitHub to ensure proper access control.

C. Creating a separate repository for each collaborator is not the standard practice for inviting team members to collaborate on a GitHub project. It is more efficient and organized to have all collaborators working within the same repository, where they can contribute, review, and manage the project together in a centralized location.

D. Sharing a link to the code repository is not the recommended way to invite a user to collaborate on a GitHub repository. While sharing the repository link may provide access to the code, it does not grant the user the necessary permissions and access levels required for active collaboration on the project. It is essential to use the built-in collaboration features within GitHub to ensure proper management of team members and their contributions.

Discussion

Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.

You must be logged in to post a comment.

Preparing For

Your Certification?

255+ certifications
Detailed explanations
Free PDF samples

Has All The Questions You Need