Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

conservative import-payload dry-run lists plate-ci.yml as would_create although ci.yml exists

Open Beginner friendly
#1,264 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the conservative import-payload dry-run with an existing ci.yml and inspect where the ci.yml to plate-ci.yml rename is added to would_create. The issue calls for a stdlib unittest and a release fragment; confirm the dry-run reports a conflict or skips the target instead of creating a second CI workflow.

Written by the indexing model from the issue text.

Description

Bug

Reported by BeamNG.magic (read from code, please reproduce first), and seen again while repairing a template-made repo. The conservative dry-run lists ci.yml -> plate-ci.yml under would_create even though ci.yml already exists, which can leave two CI workflows. The validator requires ci.yml.

Expected

The dry-run recognises the renamed target and reports a conflict or skip, never a second CI workflow.

Definition of done

stdlib unittest, release fragment, small PR with a Closes keyword.

Dominant language
Python
Stars
1
Forks
0
Avg merge
2d 10h
Merged PRs (30d)
39

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 akasper/plate

All issues in akasper/plate

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.