From 7e67714dc2efbe3ed72199841801957873ad8e59 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pablo=20Nicol=C3=A1s=20Estevez?= <pablo22estevez@gmail.com>
Date: Wed, 23 Sep 2026 17:37:59 +0100
Subject: [PATCH] Removed old issue template (#13791)

<!-- Thank you for your contribution! -->

## What do these changes do?
Remove old issue_template.md file, as the project currently uses
issue_template directory

<!-- Please give a short brief about these changes. -->

## Are there changes in behavior for the user?

No, this issue template was not accesible when creating an issue
<!-- Outline any notable behaviour for the end users. -->

## Is it a substantial burden for the maintainers to support this?

No, this should just remove an unused file
<!--
Stop right there! Pause. Just for a minute... Can you think of anything
obvious that would complicate the ongoing development of this project?

Try to consider if you'd be able to maintain it throughout the next
5 years. Does it seem viable? Tell us your thoughts! We'd very much
love to hear what the consequences of merging this patch might be...

This will help us assess if your change is something we'd want to
entertain early in the review process. Thank you in advance!
-->

## Related issue number

<!-- Will this resolve any open issues? -->
<!-- Remember to prefix with 'Fixes' if it closes an issue (e.g. 'Fixes
#123'). -->

## Checklist

- [ ] I think the code is well written N/A
- [ ] Unit tests for the changes exist N/A
- [ ] Documentation reflects the changes
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
  * The format is &lt;Name&gt; &lt;Surname&gt;.
  * Please keep alphabetical order, the file is sorted by names.
- [ ] Add a new news fragment into the `CHANGES/` folder
  * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`)
  * if you don't have an issue number, change it to the pull request
    number after creating the PR
    * `.bugfix`: A bug fix for something the maintainers deemed an
      improper undesired behavior that got corrected to match
      pre-agreed expectations.
    * `.feature`: A new behavior, public APIs. That sort of stuff.
    * `.deprecation`: A declaration of future API removals and breaking
      changes in behavior.
    * `.breaking`: When something public is removed in a breaking way.
      Could be deprecated in an earlier release.
    * `.doc`: Notable updates to the documentation structure or build
      process.
    * `.packaging`: Notes for downstreams about unobvious side effects
      and tooling. Changes in the test invocation considerations and
      runtime assumptions.
    * `.contrib`: Stuff that affects the contributor experience. e.g.
      Running tests, building the docs, setting up the development
      environment.
    * `.misc`: Changes that are hard to assign to any of the above
      categories.
  * Make sure to use full sentences with correct case and punctuation,
    for example:
    ```rst
    Fixed issue with non-ascii contents in doctest text files
    -- by :user:`contributor-gh-handle`.
    ```
    I think this doesn't require a changes file, ut happy to add it


    Use the past tense or the present tense a non-imperative mood,
    referring to what's changed compared to the last released version
    of this project.
---
 .github/ISSUE_TEMPLATE.md | 30 ------------------------------
 1 file changed, 30 deletions(-)
 delete mode 100644 .github/ISSUE_TEMPLATE.md

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
deleted file mode 100644
index 30e673f0831..00000000000
--- a/.github/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,30 +0,0 @@
-## Long story short
-
-<!-- Please describe your problem and why the fix is important. -->
-
-## Expected behaviour
-
-<!-- What is the behaviour you expect? -->
-
-## Actual behaviour
-
-<!-- What's actually happening? -->
-
-## Steps to reproduce
-
-<!-- Please describe steps to reproduce the issue.
-     If you have a script that does that please include it here within
-     markdown code markup. The chances of someone looking at your issue
-     are *vastly* improved if you provide complete code that can be
-     copy/pasted and executed directly in Python. -->
-
-## Your environment
-
-<!-- Describe the environment you have that lead to your issue.
-     This includes aiohttp version, OS, proxy server and other bits that
-     are related to your case.
-
-     IMPORTANT: aiohttp is both server framework and client library.
-     For getting rid of confusing please put 'server', 'client' or 'both'
-     word here.
-     -->