Report configuration problemas as issues in repository #2870
Description
Description
A couple of times I have faced some misconfiguration with the .packit.yaml file, where I was pointing out to the wrong username/group, or something else that prevented the pipelines to run, that was not clear until I interacted with the team and asked for some help.
It would be nice if packit could report an issue in the repository to warn the user that something is wrong with their configuration, or if any error has happened at all, sometimes, because of misconfiguration, errors may appear in packit backend, but the user does not know about it, and is left with a not working repository, like using a username instead of a group in the owner section, copr repository that does not exist etc..
Benefit
The benefit would be that the UX for the user would be much better, as we would know if something is not configured properly (or missing) immediately through our issues in the repository, helping in debugging and preventing this error in future projects.
Importance
Right now, it's very difficult to spot that you have messed up in the configuration if you don't have full knowledge about packit/copr, so, that would be very impactful for new users to have
What is the impacted category (job)?
Copr builds
Workaround
- There is an existing workaround that can be used until this feature is implemented.
Participation
- I am willing to submit a pull request for this issue. (Packit team is happy to help!)