-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
3
-
False
-
-
False
-
-
Story (Required)
tkn pac generate currently uses file matching to "detect" the primary language of a repo.
github api gives that and we could use it!
unfortunately with github app we would not be able to use a token to query that so we would need a fallback mechanism to the previous method if the repo is not public and can't query the API about it.
Background (Required)
<Describes the context or background related to this story>
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
- duplicates
-
SRVKP-3669 Integrate smart auto generation repository to tkn-pac
-
- New
-