Map of user replacements
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the configuration entry point and the code that assembles release-note drafts. Trace how each entry is produced, then determine where a string-to-string replacement map can be applied; done means configured keys are replaced in drafts, including contributor handles and linked project names as shown in the examples.
Written by the indexing model from the issue text.
Description
Background
Autoreplacemets can greatly simplify the work of the release notes creator, and improve the quality of generated release notes.
Feature
Add a setting, which would be a map string->string. Each key occurence in the release notes entry would be replaced by its value in the draft
Example usage
Contributor's name replaced for their GitHub handle
David Benedeki->@benedeki
Commonly mentioned projects or sites linked
Fa-DB->[Fa-Db](https://github.com/AbsaOSS/fa-db)
- Dominant language
- Python
- Stars
- 13
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 5
Getting set up
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/generate-release-notes
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
epic
Difficulty 5/5 Over a week Newbie friendliness 30/100
All issues in AbsaOSS/generate-release-notes
Similar issues
-
correction metadata
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
acl-org/acl-anthology#10104 · 1 comment ·
Maintainers usually reply within 1 day
-
bug status/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
prowler-cloud/prowler#12885 · 1 comment ·
Maintainers usually reply within 1 day
-
Bug in GaussianTailProbabilityCalibrator: running_statistics=False still uses a windowed varianceOpenbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
selimfirat/pysad#107 ·
Maintainers usually reply within 1 day
-
bug ci-failure high priority
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vllm-project/vllm-omni#8194 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day