Explain the importance of reproducers

[Dreamsorcerer]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.30%. Comparing base (684b792) to head (2fda9e0).
Report is 2 commits behind head on master.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #9053   +/-   ##
=======================================
  Coverage   98.30%   98.30%           
=======================================
  Files         107      107           
  Lines       34356    34356           
  Branches     4071     4071           
=======================================
  Hits        33772    33772           
  Misses        412      412           
  Partials      172      172           

Flag	Coverage Δ
CI-GHA	98.19% <ø> (ø)
OS-Linux	97.85% <ø> (ø)
OS-Windows	96.26% <ø> (ø)
OS-macOS	97.53% <ø> (+<0.01%)	⬆️
Py-3.10.11	97.63% <ø> (ø)
Py-3.10.14	97.56% <ø> (ø)
Py-3.11.9	97.79% <ø> (ø)
Py-3.12.5	97.91% <ø> (ø)
Py-3.9.13	97.51% <ø> (ø)
Py-3.9.19	97.46% <ø> (ø)
Py-pypy7.3.16	97.07% <ø> (ø)
VM-macos	97.53% <ø> (+<0.01%)	⬆️
VM-ubuntu	97.85% <ø> (ø)
VM-windows	96.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[patchback]

Backport to 3.10: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 5f5a4d2 on top of patchback/backports/3.10/5f5a4d2c320f071391a0c47ecedaf507bcb9a469/pr-9053

Backporting merged PR #9053 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.10/5f5a4d2c320f071391a0c47ecedaf507bcb9a469/pr-9053 upstream/3.10

4. Now, cherry-pick PR Explain the importance of reproducers #9053 contents into that branch:

   $ git cherry-pick -x 5f5a4d2c320f071391a0c47ecedaf507bcb9a469

   If it'll yell at you with something like fatal: Commit 5f5a4d2c320f071391a0c47ecedaf507bcb9a469 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 5f5a4d2c320f071391a0c47ecedaf507bcb9a469

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Explain the importance of reproducers #9053 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/5f5a4d2c320f071391a0c47ecedaf507bcb9a469/pr-9053

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.11: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 5f5a4d2 on top of patchback/backports/3.11/5f5a4d2c320f071391a0c47ecedaf507bcb9a469/pr-9053

Backporting merged PR #9053 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.11/5f5a4d2c320f071391a0c47ecedaf507bcb9a469/pr-9053 upstream/3.11

4. Now, cherry-pick PR Explain the importance of reproducers #9053 contents into that branch:

   $ git cherry-pick -x 5f5a4d2c320f071391a0c47ecedaf507bcb9a469

   If it'll yell at you with something like fatal: Commit 5f5a4d2c320f071391a0c47ecedaf507bcb9a469 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 5f5a4d2c320f071391a0c47ecedaf507bcb9a469

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Explain the importance of reproducers #9053 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/5f5a4d2c320f071391a0c47ecedaf507bcb9a469/pr-9053

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[bdraco]

Not sure if backport matters here as github only looks at master for the issue templates

[webknjaz]

Not sure if backport matters here as github only looks at master for the issue templates

Yes. But it may cause problems when backporting other PRs with functional changes that happen to also touch these files for whatever reason…

[webknjaz]

Personally, I'd put it into the description of the field rather than the placeholder that disappears as soon as somebody clicks on it... check the UX here https://github.com/aio-libs/aiohttp/issues/new?assignees=aio-libs%2Ftriagers&labels=bug&projects=&template=bug_report.yml

[Dreamsorcerer]

Feel free to adjust. I'm not sure how I'd format it into the description.