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

A two-way Markdown mirror

Open
  • Is something wrong?
#56 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, markdown
Domain
backend, desktop

Research direction

Start with ROADMAP.md and the existing one-way mirror in v1.4 (#37). Decide and record dated answers there for file watching, versions, conflicts, new and deleted prompt files, and workflows; the issue is done when those decisions are documented and it has a milestone with its own checklist.

Written by the indexing model from the issue text.

Description

enhancement later

Edit a prompt's Markdown file in any editor, and have the library pick the change up.

v1.4's mirror (#37) is one-way on purpose: Prompuff writes the folder, and Import is still the only way files come in. A two-way mirror waits until the one-way mirror has shipped and people use it.

What has to be settled before this gets a milestone

  • Watching. How Prompuff notices a changed file, including while it's closed, when it next opens.
  • Versions. A changed title, description, body or notes in a file becomes a new version, as in the app. A file that doesn't parse leaves the prompt alone and says why.
  • Conflicts. A prompt changed in the app and in its file since the last sync. The library keeps both as versions or asks, but never loses either one.
  • New and deleted files. Whether a new file becomes a prompt, and whether a deleted file sends its prompt to Recently deleted. Removing for good from a file seems too risky.
  • Workflows. The same questions for files in workflows/.

Done when

  • The settled answers are a dated decision in ROADMAP.md, and this issue gets a milestone with its own checklist.
Dominant language
C#
Stars
0
Forks
1
Avg merge
1h 21m
Merged PRs (30d)
22

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 hazeliscoding/prompuff

All issues in hazeliscoding/prompuff

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.