Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPIKE: Research templating #201

Open
3 tasks
lachmanfrantisek opened this issue Sep 5, 2023 · 0 comments
Open
3 tasks

SPIKE: Research templating #201

lachmanfrantisek opened this issue Sep 5, 2023 · 0 comments
Labels
area/config Related to the Packit's configuration. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/feature New feature or a request for enhancement.

Comments

@lachmanfrantisek
Copy link
Member

We've got a couple of requests for config templating. Let's spend a while researching various options and use cases.

related issues:

The task of this is to create a new document and:

  • Summarise the use cases -- e.g. monorepo (e.g. Copr or some layered distributions) or a couple of similar packages maintained by the same person (e.g. Forman).
  • Suggest implementation.
  • Cleanup/(re)define the existing issues. Create an epic if needed.
@lachmanfrantisek lachmanfrantisek added kind/feature New feature or a request for enhancement. area/config Related to the Packit's configuration. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. impact/low This issue impacts only a few users. and removed impact/high This issue impacts multiple/lot of users. labels Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/config Related to the Packit's configuration. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/feature New feature or a request for enhancement.
Projects
Status: backlog
Development

No branches or pull requests

1 participant