devcrocod / octokod Goto Github PK

This task involves a comprehensive study of the GitHub API, aimed at understanding the structure of requests and responses, identifying any rate limitations, and discovering other relevant details

The library architecture should be designed keeping in mind the defined core features and the intricacies of the GitHub API. This step involves deciding on the library's overall structure, choosing the design patterns, error handling mechanisms, and more.

To ensure the viability of design decisions and to foresee any potential challenges, it's essential to develop prototypes or proofs of concept for key components of the library. The prototypes should be as minimal as possible, with the aim to verify assumptions and achieve functionality quickly.

Identify and define the core functionalities the library will provide

This task involves creating models that represent the various objects within the GitHub API. The models should reflect all the attributes provided by the GitHub API for each object and adhere to the structure of the API's responses.

Additionally, unit tests should be written for each model to ensure its proper functionality and validate that the models correctly mirror the structure of the GitHub API's responses.

• generate models via github openapi
• adapt models
• write unit tests

models:

• Actions #5
• Activity #6
• Apps #7
• Billing #8
• Branches #9
• Checks #10
• Codes of conduct #11
• Code Scanning #12
• Codespaces #13
• Collaborators #14
• Commits #15
• Copilot #16
• Dependabot #17
• Dependency graph #18
• Deploy Keys #19
• Deployments #20
• Emojis #21
• Gists #22
• Git database #23
• Gitignore #24
• Interactions #25
• Issues #26
• Licenses #27
• Markdown #28
• Meta #29
• Metrics #30
• Migrations #31
• Organizations #32
• Packages #33
• Pages #34
• Projects #35
• Pulls #36
• Rate Limit #37
• Reactions # 38
• releases #39
• Repositories #40
• Search #41
• Secret scanning #42
• Security advisories #43
• Teams #44
• Users #45
• Repository webhooks #46