Duplicate entries are still created even if setting is None

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, python
Domain
devops

Research direction

Start by reading the attached release_draft.yaml and tracing how the action parses duplicity-scope and decides whether to create duplicate entries. Reproduce the issue with the supplied configuration and identify the relevant tests or entry point from that flow. Done means a none setting creates no duplicate entries and the behavior is covered by a regression test.

Written by the indexing model from the issue text.

Description

bug
Describe the bug

Even if
duplicity-scope: 'none'
duplicate entries are still created.

Steps to Reproduce

Configuration attached.

Expected state

Duplicates behave per setting.

Impact / Severity

Medium

Attachments / Evidence

release_draft.yaml

image
Desktop

No response

Related / References

No response

Dominant language
Python
Stars
12
Forks
0
Avg merge
1m
Merged PRs (30d)
6

Getting set up

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 AbsaOSS/generate-release-notes

All issues in AbsaOSS/generate-release-notes

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.