Conversation
Thank you!Thank you for your pull request 😃 🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}. If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
Rendered Changes🔍 Inspect the changes: https://github.com/esciencecenter-digital-skills/python-intermediate-development/compare/md-outputs..md-outputs-PR-3 The following changes were observed in the rendered markdown documents: What does this mean?If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation. ⏱️ Updated at 2025-10-23 19:52:24 +0000 |
Co-authored-by: Sander van Rijn <svr003@gmail.com>
Co-authored-by: Sander van Rijn <svr003@gmail.com>
Co-authored-by: Sander van Rijn <svr003@gmail.com>
Co-authored-by: Sander van Rijn <svr003@gmail.com>
…thon-intermediate-development into ruff-fn
|
Thanks for the nice feedback @sjvrijn , I have included your suggestions! Do you have any other comments, or do you think this could be merged? |
Auto-generated via `{sandpaper}`
Source : 8eb382b
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-10-24 12:41:06 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : 4848931
Branch : main
Author : Francesco Nattino <49899980+fnattino@users.noreply.github.com>
Time : 2025-10-24 12:40:11 +0000
Message : Merge pull request #3 from esciencecenter-digital-skills/ruff-fn
Use Ruff as linter
Drop pylint in favour of Ruff.
This could cover part of carpentries-incubator#491