How prek handles ideas and feature requests

[j178]

Ideas and feature requests are welcome. Please search existing discussions first, then start a new topic in the Ideas category rather than opening an issue directly.

prek is primarily a personal project, so I cannot maintain a detailed roadmap or provide an individual status for every proposal.

An open discussion does not mean that a feature has been accepted or planned. It generally means one of two things:

1. There is not yet a clear implementation path. The discussion remains open to collect more use cases, feedback, and possible solutions.
2. The proposal is not currently part of my plans. It may remain open to gauge broader interest, but may eventually be closed if no meaningful feedback or viable implementation path emerges.

Once a proposal is sufficiently clear, fits prek's direction, and has a realistic implementation path, a linked issue can be created to track the work. An issue means that the proposal is actionable enough to track. It does not guarantee priority, a timeline, or eventual inclusion.

Concrete use cases, limitations of existing workarounds, tradeoffs, and simple implementation ideas are especially helpful. Reactions and comments indicate interest, but they are not a vote.

If you would like to contribute an implementation, please discuss it first. Do not invest in a substantial pull request until the direction and scope have been agreed and a corresponding issue exists. Issues labeled help wanted or good first issue are ready for contributors.

Closing a discussion keeps the active list useful. It does not erase the history, and an idea can be reconsidered if new information or a better implementation approach emerges.