16:31 <d1b2> <widlarizer> I think writing docs that cross projects and tools like this aren't a good idea, because it implies responsibility for integrating with other projects that are maintained by other people. That's why I called it a blogpost, it would be helpful as an external source, but if I were maintaining amaranth, since it doesn't provide an interface to github actions, it's not documenting the project (amaranth). I suggest moving your sby

16:31 <d1b2> integration script etc into your own repository, using the issue body as the readme, and tagging it with the github topic "amaranth-hdl"

16:33 <d1b2> <widlarizer> If you do that, you can definitely ask to have a link to your use case docs added to the links at https://amaranth-lang.org/docs/amaranth/latest/tutorial.html