DevOps / Github Interview questions
Explain the lifecycle of a GitHub issue from creation to closure?
An issue moves through a fairly predictable path from being reported to being resolved, though the exact stops depend on how a team configures labels and projects.
Creation often starts from an issue template, which standardizes what information a reporter provides. Triage adds labels (type, priority, area) and an assignee, making the issue visible on the relevant Project board. Once picked up, a contributor typically opens a pull request referencing the issue with a closing keyword like Fixes #123 or Closes #123.
When that pull request merges, GitHub automatically transitions the linked issue to closed, no manual step required, which keeps Project boards accurate without someone having to remember to close tickets by hand.
More Related questions...