Details
-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
None
-
False
Description
Story (Required)
As a trusted user with permission to push to branches inside repository trying to create pull-request in the repository I want that PaC pipelineruns are triggered so that I do not need to be owner/collaborator/public member or in owner files.
Background (Required)
When I have write permission in github to create branch in owner repository then I do not see reason why should I be in OWNER file. Typical usage for this are bots, eg. dependabot -> repository owner installed the bot so the bot is trusted.
Current requirement: https://pipelinesascode.com/docs/guide/running/ - idea is to apply this only on Pull-requests coming from fork repositories.
Out of scope
<Defines what is not included in this story>
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met