Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Configurable Parameter for Repository Type at Program Invocation #13

Open
B3J4y opened this issue Jul 29, 2023 · 0 comments
Open

Comments

@B3J4y
Copy link
Contributor

B3J4y commented Jul 29, 2023

(Text generated by ChatGPT)

In our current implementation, we deduce the repository type (Github or Gitlab) based on certain heuristics from the repository URL. This approach, while functional for most common use cases, may not always yield accurate results, especially when dealing with non-standard URLs or self-hosted repositories.

To enhance our code's flexibility and reliability, we need to implement an additional feature where the user can specify the repository type (Github or Gitlab) via a parameter during the program invocation. This configurable parameter will allow users to manually select the repository type, thus overriding the heuristic deduction from the URL.

This feature should entail the following:

  1. The addition of a new parameter (e.g., --repo-type) at the program invocation. Valid inputs for this parameter should be 'Github' or 'Gitlab'.
  2. Modifying the codebase to accept and utilize this parameter in determining the repository type.
  3. If this parameter is not provided, the program should fall back to its current behavior of determining the repository type based on the URL.

By implementing this feature, we can ensure that our program accurately handles Github and Gitlab repositories regardless of how their URLs are structured. This improvement will greatly enhance our program's usability and reliability, particularly for users with non-standard or self-hosted repositories.

Note: Ensure that adequate validation checks are in place to handle any potential errors or misconfigurations by the user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant