Domain 3: Collaboration Features - Deck 1 Flashcards
Q54: What are the possible statuses for a pull request review? (Choose three.) [ghcertified]
a) Applaud
b) Deny
c) Approve
d) Close
e) Comment
f) Request Changes
C,E,F
Q51: Which information can be found in the Pulse section in the Insights tab of a repository? (Choose four) [ghcertified]
a) Amount of forks of the repo
b) Pull requests open/merged ratio
c) Summary of repository activity
d) List of unresolved conversations
e) List of issue discussions
f) Amount of code line additions and deletions
B,C,D,F
Describe how to link a PR to an issue
You can link a pull request to an issue using a keyword in the comments, such as “close(s/d)”, “fix(es/ed)”, or “resolve(s/d)”, followed by the issue number.
Alternatively, you can manually link up to ten issues per pull request by navigating to the pull request page, clicking “Development,” and then selecting the issue you wish to associate. Both the issue and pull request must be within the same repository.
The process for linking through the issue itself follows the same steps
How can you link a pull request to an issue in GitHub? [Describe how to link a PR to an issue]
a) By using a keyword like “closes” in the pull request description, followed by the issue number.
b) By manually linking the issue to the pull request from the pull request page.
c) All of the above.
C
Describe how to create an issue
The most common method is to navigate to the repository’s “Issues” tab, click “New issue,” and then enter a title and description for the issue.
Alternatively, you can use the GitHub CLI command “gh issue create” to create an issue.
Other methods include creating issues from comments, code, discussions, projects, task lists, URL queries, and code scanning alerts.
Question 1: What are the two most common ways to create an issue on GitHub?[Describe how to create an issue]
a) Using the GitHub CLI command “gh issue create” and creating a branch.
b) Navigating to the “Issues” tab and clicking “New issue” and using the GitHub CLI command “gh issue create”.
c) Creating from the notifcation and using git flow.
B
Aside from the two most common ways, what are other ways to create an issue on GitHub?[Describe how to create an issue]
a) Using Git commands like “git add” and “git commit” and using codespaces.
b) Creating a branch from the issue and using Git flow.
c) Creating an issue from comments, code, discussions, projects, task lists, URL queries, and code scanning alerts.
C
Describe the difference between an issue, discussion, and pull request
An issue is a way to track improvements, tasks, or bugs for work on GitHub, acting as a primary tool for collaborative problem-solving within a repository.
Discussions, on the other hand, provide a space for community members to engage in conversations and share ideas, questions, or comments, focusing on open dialogue rather than task tracking or problem reporting.
A pull request is a way to propose changes to the codebase, suggesting that your changes be merged into the main code.
Which of the following options has the correct description? [Describe the difference between an issue, discussion, and pull request]
a) Discussion: A discussion is a way to track improvements, tasks, or bugs for work on GitHub. It is a primary tool for collaborative problem-solving within a repository.
b) Issue: An issue is a way to propose changes to the codebase. By opening an issue, you are suggesting that your changes be merged into the main code.
c) Pull Request: A pull request is a way to track improvements, tasks, or bugs for work on GitHub. It is a primary tool for collaborative problem-solving within a repository.
d) Discussion: A discussion is a feature that provides a space for community members to engage in conversations and share ideas, questions, or comments. It’s more about having an open discussion than tracking tasks or reporting problems like issues.
D
Explain how to create a branch from an issue
1) To create a branch from an issue, in the repository, navigate to the issue page.
2) In the right side menu, in “Development”, click in “Create a branch”.
3) Give the branch a name, select the repository. destination and choose if you want to work on the branch locally or open it in GitHub Desktop.
Identify how to assign issues
1) In the main page of the repository, click in “Issue” or “Pull Request”
2) In the right side menu, click “Assignees”.
3) Start typing their username, then click their name when it appears.
You can select and add up to ten assignees to an issue or pull request.
Describe how to search and filter issues
1) In the main page of the repositor, click in Issue or Pull Request
2) Above the list, select the Filters dropdown menu, then click the type of filter you’re interested in.
The “Filters” dropdown menu allows you to view open or created issues and pull requests, those assigned to you, and those where you are mentioned.
You can also search by search, label, assignee, author, milestone, and use advanced filters
What can you search for using the “Filters” dropdown menu? [Describe how to search and filter issues]
a) All open issues and pull requests, Issues and pull requests created by you, assigned to you, or where you are mentioned.
b) Specific keywords, labels, and milestones.
c) Open and closed issues, specific mentions, comments, and timeframes.
A
Alternative methods for filtering issues without the filter dropdown: [Describe how to search and filter issues]
- S___ b
- L______
- Au_____
- Ass__
- M_____
- A_______ F______
- search bar
- label
- assignee
- author
- milestone
- dvanced filters
Describe how to pin an issue
1) navigate to the main page of the repository.
2) Click “Issue”
3) In the list of issues, click the issue you’d like to pin.
4) In the right sidebar, click Pin issue.
