openSUSE / openSUSE/doc-kit

Initial: is tricky

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cat-bug scope-tool
Dominant language
Shell
Stars
5
Forks
3
Avg merge
2d 15h
Merged PRs (30d)
1

Description

There are a few issues with how Initial: is implemented currently:

  • The SHA sums of Initial: files will only be listed in the user repo's doc-kit.conf after the setup but will vanish on subsequent updates
  • initial: files that are newly added to the MANIFEST will never be downloaded by existing setups

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.

Research direction

Read the setup and update paths that write the user repository's doc-kit.conf and process MANIFEST entries. Trace how Initial: files are handled after initial setup, then verify that their SHA sums persist in doc-kit.conf and that newly added initial: files download during later updates.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.