-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
area/generalNot tied to a specific areaNot tied to a specific areacomplexity/single-taskRegular task; should be done within daysRegular task; should be done within dayskind/internalTask that doesn't affect users directlyTask that doesn't affect users directly
Description
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
Metadata
Metadata
Assignees
Labels
area/generalNot tied to a specific areaNot tied to a specific areacomplexity/single-taskRegular task; should be done within daysRegular task; should be done within dayskind/internalTask that doesn't affect users directlyTask that doesn't affect users directly
Type
Projects
Status
backlog