[Bug]: Broken links in community meeting notes cause production build to fail

Open Beginner friendly
#692 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet

Research direction

Inspect the meeting notes at /community/meeting/notes/2021-07-15/ and /community/meeting/notes/2023-06-15/ and check repository history for the referenced PDFs. Run yarn build after recovering the files or updating/removing the broken references; done means the production build completes without broken-link errors.

Written by the indexing model from the issue text.

Description

Consisely describe the issue

Description

The production build fails because two community meeting notes contain links to PDF files that are not present in the repository.

The affected meeting notes are :

  • /community/meeting/notes/2021-07-15/ -> ./Podman_Image_SCP.pdf
  • /community/meeting/notes/2023-06-15/ -> ./AuriStor-ACA-PodmanCabal.pdf

Running yarn build results in:

  • Podman_Image_SCP.pdf not found
  • AuriStor-ACA-PodmanCabal.pdf not found

Expected behavior

The production build should complete successfully without broken links.

approach

Verifying whether the referenced PDFs can be recovered from the original meeting records or repository history. If they are no longer available, update or remove the broken references accordingly.

Upload screenshots or screen recordings

Add screenshots or screen recordings to help explain your problem.

LLM Policy
  • This issue is human-written, and folow up comments will also be human-written
Dominant language
TypeScript
Stars
108
Forks
188
Avg merge
3d 14h
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

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 containers/podman.io

All issues in containers/podman.io

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.