When searching for Changelog, the results don't specify what component they are for
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by inspecting the plugin_template and the generated changelog output used by search results. Reproduce a search for "Changelog" and trace how each result is labeled; the work is done when every result identifies its component clearly.
Written by the indexing model from the issue text.
Description
We need to make it so that when searching for "Changelog" I can tell what component each "Changelog" in the list of results is for.
Since changelogs are auto-generated, this could probably be handled via the plugin_template?
The following screenshot illustrates the problem:
- Dominant language
- HTML
- Stars
- 2
- Forks
- 17
- Avg merge
- 7d 18h
- Merged PRs (30d)
- 3
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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 pulp/pulp-docs
-
epic
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Add issue templatesOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
[Sync EN] Fix session read handler docs: false reports a failure, not a missing session (#5902)Opensync-en
Difficulty 2/5 1-2 days Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
unixorn/awesome-zsh-plugins#2285 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
astrodbtoolkit/astrodb-bot#105 ·