Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Transform examples in docs into included source files

Open
#819 0 comments 1 reaction 0 assignees View on GitHub

@alexchen-sys is already working on this.

Since Jul 16, 2026.

  • #826 by @alexchen-sys — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Read the svcs docs examples linked in the issue and review the related discussion in #817 to understand the proposed pattern. Then inspect the documentation examples in structlog and identify which source snippets should become included files; done means those examples are verifiable while remaining included in the docs. Pull request #826 is already open, so this work is underway.

Written by the indexing model from the issue text.

Description

A successful examples of this is https://github.com/hynek/svcs/tree/main/docs/examples

We’ve had the case of errors in recipes before and we’ve hit a similar dilemma in #817 again. Source code that isn’t a doctest should still be somehow verifiable.

cc @sirosen

Dominant language
Python
Stars
5k
Forks
302
Avg merge
17m
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hynek/structlog

All issues in hynek/structlog

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.