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

Provide a dedicated page with GitHub app commands #573

Open
TomasTomecek opened this issue Dec 14, 2022 · 5 comments
Open

Provide a dedicated page with GitHub app commands #573

TomasTomecek opened this issue Dec 14, 2022 · 5 comments

Comments

@TomasTomecek
Copy link
Member

/packit help is a solution but clutters PR

We should instead have a dedicated page where all commands are listed and documented.

@lachmanfrantisek
Copy link
Member

Maybe just add a new comment with a link to the doc page? (So we don't need to have that info in the packit-service code.)

@lachmanfrantisek lachmanfrantisek added area/user-experience Usability issue and removed area/user-experience Usability issue labels Dec 14, 2022
@lachmanfrantisek
Copy link
Member

lachmanfrantisek commented Dec 14, 2022

We should instead have a dedicated page where all commands are listed and documented.

Do we want to have this for all the jobs in one place? Or document this for each job separatelly?

@TomasTomecek
Copy link
Member Author

The ask was that it's hard to find all the supported /packit commands as they are spread all over our documentation. So ideally a single page or group of pages per command.

@lachmanfrantisek
Copy link
Member

I would say we already have something like that:
https://packit.dev/docs/guide/#how-to-re-trigger-packit-actions-in-your-pull-request

To improve that, we can generalise the text/title (= include issue comments) and link it from other places.

@TomasTomecek
Copy link
Member Author

Yes, true, but there is also propose_downstream, verify-fas, vm-image-build... :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: backlog
Development

No branches or pull requests

2 participants