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

Improve UX #20

Open
4 tasks
mfocko opened this issue Nov 15, 2024 · 0 comments
Open
4 tasks

Improve UX #20

mfocko opened this issue Nov 15, 2024 · 0 comments
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@mfocko
Copy link
Member

mfocko commented Nov 15, 2024

User (Packit Developer) story:

  • I should be able to do an (empty) amend and force push to all of the “hello world” repos without thinking about the technical details (kind of forge, public vs self-deployed instance, etc.)
    • It might be beneficial to have write access with the Packit SSH keys and reuse those (as the amount of various instances grows and it might be annoying for all members of Packit Team to set up separate accounts)
    • This use case is required for “refreshing” of statuses once Fedora branching happens
  • I should be able to easily create a test (regardless of how it should be triggered) without the many additional steps (e.g., for PRs script should create a branch, I can create the test, commit it, and script should finish the rest, i.e., push it everywhere, create PRs and set them up accordingly by itself)
  • As a Service Guru I should be able to list all the tests for each forge (e.g., table) with their results
  • If needed, I should be able to easily edit any of the tests and propagate the results
@majamassarini majamassarini added complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. area/general Related to whole service, not a specific part/integration. labels Nov 19, 2024
@majamassarini majamassarini moved this from new to backlog in Packit Kanban Board Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Status: backlog
Development

No branches or pull requests

2 participants