How congson95dev/git-handler works
Main Components
• Script Components: Clearly mark the individual scripts—create_tag.sh, delete_tag.sh, and create_pr.sh—as the core functional units. Each script provides a specific operation across multiple repositories.
• Configuration & Permissions: Include a component that represents configuration steps (e.g., permission granting with chmod, environment configuration).
• Multiple Repositories Environment: Since the use-case involves operating on multiple repositories (organized under a “prefix-folder”), incorporate these as a collective external component that the scripts act upon.
Relationships and Interactions
• Verify configuration and permissions.
• Interact with the external git-handler configuration.
• Call GitHub CLI (gh) when creating pull requests.
• Perform tag operations on multiple repositories.
• External Communication: Indicate that create_pr.sh relies on an external process (gh CLI installation) which subsequently triggers interactions with GitHub for authentication and pull request management.
Architectural Patterns and Design Principles
• Script-based Utility Tool: Emphasize that this solution is implemented as lightweight scripting, meaning it is essentially a “glue” tool coordinating operations over other repositories.
• Modularity: Even though the code base is small, treat each script as an independent module offering a single responsibility aligned with standard modular design.
• Procedural Flow: Illustrate a linear process design which starts from user command execution and flows into operations on multiple independent repositories.
Included Technologies, Frameworks, and Libraries
• Shell Scripting environment (bash or sh)
• Git for version control
• GitHub CLI (gh) as an external tool for pull request creation and GitHub interaction
• Standard Linux tools for permissions and package installation (e.g., wget)