GitHub Projects Default Workflows: Auto-archive, Item closed, Pull request merged
Which of the following default workflows are available as part of GitHub projects? (Choose three.)
Community Insight
The question tests recognition of GitHub's pre-configured workflow templates versus custom or non-existent event triggers.
This question tests knowledge of the built-in automation workflows available in GitHub Projects. The correct answer identifies three specific default triggers: auto-archiving items, handling item closure, and reacting to pull request merges.
Learners often select 'Label added to issue' because it is a common trigger for GitHub Actions, but it is not one of the native default project board workflows listed in this context.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
GitHub Projects includes several pre-built automation rules (workflows) that can be toggled on without writing code. Based on the options provided and community consensus, "Auto-archive items" (A), "Item closed" (C), and "Pull request merged" (D) are the valid choices. "Auto-archive items" allows projects to automatically move completed items to an archive section based on criteria like date or status. "Item closed" is a standard workflow that updates the card status when the underlying issue or PR is closed. "Pull request merged" is another core workflow that triggers actions when a linked PR is successfully merged.Why the Other Options Are Wrong
"Label added to issue" (B) and "Pull request opened" (E) are valid events in GitHub's broader ecosystem (e.g., for GitHub Actions), but they are not typically listed as the primary default project board workflows in this specific exam context. While you can build automations around these, the question asks for the available default workflows which usually refer to the high-level board state changes like closing, merging, or archiving.Community Comment Notes
Community feedback strongly supports ACD. One user noted that after creating a project, the visible workflows include "Auto-add sub-issues," "Auto-close issue," "Item added to project," "Item closed," "Pull request linked to issue," "Pull request merged," "Auto-add to project," "Auto-archive items," "Code changes requested," "Code review approved," and "Item reopened." This list confirms that B and E are not in the top-tier default set implied by the question.Exam Strategy
Focus on the difference between GitHub Actions triggers and GitHub Projects native automations. Remember that Project workflows often relate to the lifecycle state of the card itself (open, closed, archived) rather than granular event data like labels or open times.
Frequently Asked Questions
Why is 'Label added to issue' not a default project workflow?
While label changes are powerful triggers for GitHub Actions, they are not among the pre-configured board state automations like 'Item Closed' or 'Auto-archive'.
Can I create custom workflows if defaults aren't enough?
Yes, you can use GitHub Actions for complex logic, but the exam focuses on the out-of-the-box features available directly within the Projects UI.