fix: gitlab support improvements

[gowoons]

• Fixing README to use --setupTarget when using configure instead of --ci
• Mask API key when setting up for gitlab
• Change gitlab PR template

[github-actions]

Risk Level 2 - /home/runner/work/code-review-gpt/code-review-gpt/src/configure/index.ts

The code is generally well-written and follows good practices. However, there are a few areas that could be improved for better error handling and code readability.

1. Error Handling: The execSync function is used without any error handling mechanism. If the command fails, it will throw an error which is not caught. This can lead to unhandled promise rejections. It would be better to wrap the execSync calls in a try-catch block to handle potential errors.

try {
  execSync(`gh auth status || gh auth login`, { stdio: \"inherit\" });
  execSync(`gh secret set OPENAI_API_KEY --body=${apiKey}`);
} catch (error) {
  logger.error('Error executing command', error);
}

2. Code Duplication: The code for prompting the user for the API key is duplicated in both configureGitHub and configureGitLab functions. This could be extracted into a separate function to avoid code duplication.

const promptForApiKey = async () => {
  const inquirer = await import(\"inquirer\");
  const { apiKey } = await inquirer.default.prompt([
    {
      type: \"input\",
      name: \"apiKey\",
      message: \"Please input your OpenAI API key:\",
      mask: \"*\",
    },
  ]);
  return apiKey;
};

Then you can use this function in both configureGitHub and configureGitLab functions.

const apiKey = await promptForApiKey();

---

👍🔧🔂

---

Powered by Code Review GPT

[github-actions]

Test results summary:

✅ [PASS] - Test case: Bad variable name
✅ [PASS] - Test case: Exposed secret
✅ [PASS] - Test case: Too many nested loops
✅ [PASS] - Test case: Unawaited Promise

SUMMARY: ✅ PASS: 4 - ⚠️ WARN: 0 - ❌ FAIL: 0

---

Tests Powered by Code Review GPT

[mattzcarey]

Niceee