Remove the one-off tutorial workflow
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, yaml
- Domain
- ci-cd
Research direction
The workflow to remove is .github/workflows/tutorial-by-tag.yml, which runs on every pull request. Confirm the file is still tracked with git ls-files .github/workflows/tutorial-by-tag.yml, then read the issue's linked run and #107 for context. Done means the workflow file is deleted and no pull request check runs it, or, if the alternative is chosen, .github/CONTEXT.md names it with the pin-update step added.
Written by the indexing model from the issue text.
Description
Description of Technical Debt
#107 added .github/workflows/tutorial-by-tag.yml to run the tutorial's workflow
(docs/tutorials/gh-source-to-markdown.md § 2) once, with the three actions called by tag over the testbed's
core at 36a0ee6. Its run was green, and its six files were byte-identical to the release milestone's release-view
documents: https://github.com/AbsaOSS/living-doc/actions/runs/43265924867. The commit that was to delete the workflow
never landed, so it is on master and runs on every pull request. #107's body also links no run (it still carries a
<RUN_URL> placeholder); the link above is that run.
Impact of Technical Debt
- About a minute of CI on every pull request, and a red check if a released tag or the pinned testbed commit changes.
- No page names the workflow, so it reads as a standing check nobody decided on.
Category
DevOps / Infrastructure
Priority
Medium - Should be addressed soon
Proposed Solution
Delete .github/workflows/tutorial-by-tag.yml. Alternative, if the tutorial should stay proven on every PR: keep it, name it in .github/CONTEXT.md, and move its testbed commit and tags in each release's pin PR.
Effort Estimate
1 hour
Dependencies / Related
#106, #107
Additional Context
Measured 2026-11-12 at living-doc 2df73dc. Re-check:
git ls-files .github/workflows/tutorial-by-tag.yml prints the path while this is open.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 14m
- Merged PRs (30d)
- 27
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AbsaOSS/living-doc
-
type:tech-debt
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
AbsaOSS/living-doc#130 ·
Maintainers usually reply within 1 day
-
type:tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AbsaOSS/living-doc#129 ·
Maintainers usually reply within 1 day
-
type:tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AbsaOSS/living-doc#119 ·
Maintainers usually reply within 1 day
-
type:tech-debt
Difficulty 5/5 Over a week Newbie friendliness 5/100
AbsaOSS/living-doc#136 ·
Maintainers usually reply within 1 day
-
type:tech-debt
Difficulty 4/5 1-2 days Newbie friendliness 18/100
AbsaOSS/living-doc#135 ·
Maintainers usually reply within 1 day
All issues in AbsaOSS/living-doc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
deepchem/deepchem#5289 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
UKGovernmentBEIS/inspect_evals#2892 · 1 comment ·
Maintainers usually reply within 1 day
-
Versioning docs: say that no output from the 0.46 warning check means nothing is affectedPossibly taken @grelinfo claimed this today. Opendocumentation priority:low size:S
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
alphacrack/readme2demo#293 ·