{
  "id": 3275828,
  "title": "HD-101 — The first pull request",
  "url": "https://urgent.news/2026/08/25/hd-101-the-first-pull-request",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-25T14:08:50.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/nazmur96/hd-101-the-first-pull-request-2fep"
  },
  "original_language": "en",
  "account": "HD-101 - The First Pull Request\n\nThis ticket outlines the process of creating a pull request (PR) in a software development workflow. The PR, named HD-101: filter tickets by priority, was opened to add a feature to the helpdesk CLI that prioritizes tickets based on their priority level.\n\nTo create the PR, the following steps were taken:\n1. Git switch -c hd-101-priority-filter: This command creates a new branch named 'hd-101-priority-filter' based on the current branch.\n2. Code was written in this new branch.\n3. Changes were added (git add -A) and committed (git commit -m 'feat: filter tickets by priority').\n4. The branch was pushed to the 'origin' remote (git push -u origin hd-101-priority-filter).\n5. A PR was created using the GitHub command-line tool (gh pr create) with the following specifications:\n- Base branch: 'main'\n- Head branch: 'hd-101-priority-filter'\n- Title: HD-101: filter tickets by priority\n- Body: Adds --priority to the list command.\n\nAfter the PR was created and merged, it was noted that there were no tests running, no required reviewers, and no status checks. This demonstrates that the PR was essentially an empty change, serving as an example of a PR without any necessary gatekeeping measures.\n\nA key point to understand is the distinction between a PR's base and head. The base is the destination where the code will land (in this case, the 'main' branch), while the head is the source branch that the code originates from (in this case, 'hd-101-priority-filter'). Confusing these two terms can lead to mistakes, as seen in the referenced mistakes.md file.\n\nLastly, it is important to note that a PR's head has no relation to Git's HEAD pointer. Git's HEAD refers to the current commit being pointed at, while a PR's head refers to the branch that is being proposed for merging.",
  "summary": "HD-101 — The first pull request Builds: nothing. Teaches: why the next six tickets exist. The ticket Add a feature to the helpdesk CLI. Don't push to main — open a pull request. What you do git switch -c hd-101-priority-filter # ... write the code ... git add -A git commit -m \"feat: filter tickets by priority\" git push -u origin hd-101-priority-filter gh pr create --base main --head…",
  "key_points": [
    "HD-101 is a pull request for adding a feature to prioritize tickets in a helpdesk CLI.",
    "The PR lacked tests, reviewers, and status checks, serving as an example of an empty change."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}