Add blog post: Issues vs pull requests - problems versus solutions

[Copilot]

The issue outlined a framework distinguishing issues (problem definition) from pull requests (solution implementation). Created a blog post explaining this separation.

Changes

• New post: _posts/2025-11-15-issues-are-not-pull-requests.md
  • Defines issues as problem space: what to solve, whether to solve it, relative importance, user-facing solution
  • Defines PRs as solution space: technical implementation quality, coding standards, edge cases
  • Covers why the distinction matters (async collaboration, diverse perspectives, better documentation)
  • Provides ideal workflow and exceptions

Front Matter

title: Issues are not pull requests
description: Understanding the distinction between defining problems in issues and proposing solutions in pull requests is fundamental to effective software collaboration and can dramatically improve your team's workflow.

The post follows existing site conventions (required front matter, github-culture footer, Ben's writing style).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https (dns block)
• https://api.github.com/repos/benbalter/benbalter.github.com/pages
  • Triggering command: ruby3.2 /home/REDACTED/work/benbalter.github.com/benbalter.github.com/vendor/bundle/ruby/3.2.0/bin/rake build (http block)
  • Triggering command: ruby3.2 /home/REDACTED/work/benbalter.github.com/benbalter.github.com/vendor/bundle/ruby/3.2.0/bin/jekyll build (http block)
  • Triggering command: ruby3.2 /home/REDACTED/work/benbalter.github.com/benbalter.github.com/vendor/bundle/ruby/3.2.0/bin/jekyll build --config _config.yml,_config_test.yml (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Issues and pull requests, problems versus solutions</issue_title>
<issue_description>Issues:

• What is the problem?
• Is this a problem we should be solving?
• What's the relative importance of solving this problem?
• What's the best (user-facing) solution to this problem?

Pull requests:

• Is this the right technical solution to the previously-agreed-upon problem?
• Is the technical solution implemented properly?
  </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Issues and pull requests, problems versus solutions #422

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull Request Overview

This PR adds a comprehensive blog post explaining the distinction between GitHub Issues (problem definition) and Pull Requests (solution implementation). The post promotes better software development workflow by encouraging teams to separate "what to build" discussions from "how to build it" reviews.

Key Changes:

• New blog post explaining issues vs. pull requests conceptual framework
• Covers why separation matters: async collaboration, diverse perspectives, better documentation
• Provides ideal workflow and practical guidance

Reviewed Changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
_posts/2025-11-15-issues-are-not-pull-requests.md	New blog post with proper front matter, well-structured content following site conventions, includes github-culture footer
assets/images/og/posts/issues-are-not-pull-requests.png	Open Graph social media preview image matching post slug naming convention