➤  rustup update                    
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: checking for self-updates

  stable-x86_64-unknown-linux-gnu unchanged - rustc 1.67.0 (fc594f156 2023-01-24)

info: cleaning up downloads & tmp directories
╰─➤  cat .git/hooks/prepare-commit-msg
───────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: .git/hooks/prepare-commit-msg
───────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ #!/bin/sh
   2   │ 
   3   │ ### BEGIN GPTCOMMIT HOOK ###
   4   │ gptcommit prepare-commit-msg --commit-msg-file "$1" --commit-source "$2" --commit-sha "$3"
   5   │ ### END GPTCOMMIT HOOK ###
───────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
╰─➤  RUST_LOG=trace git commit
the input device is not a TTY

$ gptcommit config set openai.api_base "XXXXXXX" -v
2023-03-27T08:22:20.551Z DEBUG [gptcommit::settings] Using home dir at /Users/Bobot
2023-03-27T08:22:20.551Z DEBUG [gptcommit::settings] Found config dir at /Users/Bobot/.config/gptcommit
2023-03-27T08:22:20.551Z DEBUG [gptcommit::settings] Applying config file at /Users/Bobot/.config/gptcommit/config.toml
2023-03-27T08:22:20.558Z INFO  [gptcommit::git] Repo path from git: Output { status: ExitStatus(unix_wait_status(0)), stdout: "/Users/Bobot/Repositories/xvautomator\n.git/hooks\n", stderr: "" }
2023-03-27T08:22:20.558Z INFO  [gptcommit::git] Creating dir at .git/hooks
2023-03-27T08:22:20.558Z DEBUG [gptcommit::settings] Applying config from  GPTCOMMIT__*: Ok({"openai_api_base": Value { origin: Some("the environment"), kind: String("XXXXXXXX") }})
2023-03-27T08:22:20.559Z DEBUG [gptcommit] Settings: Settings { model_provider: Some(OpenAI), openai: Some(OpenAISettings { api_key: Some("my-personal-key"), model: Some("gpt-3.5-turbo"), retries: Some(2) }), prompt: Some(PromptSettings { conventional_commit_prefix: Some("You are an expert programmer, and you are trying to summarize a code change.\nYou went over every file that was changed in it.\nFor some of these files changes where too big and were omitted in the files diff summary.\nDetermine the best label for the commit.\n\nHere are the labels you can choose from:\n\n- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)\n- chore: Updating libraries, copyrights or other repo setting, includes updating dependencies.\n- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, GitHub Actions)\n- docs: Non-code changes, such as fixing typos or adding new documentation\n- feat: a commit of the type feat introduces a new feature to the codebase\n- fix: A commit of the type fix patches a bug in your codebase\n- perf: A code change that improves performance\n- refactor: A code change that neither fixes a bug nor adds a feature\n- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)\n- test: Adding missing tests or correcting existing tests\n\n\nTHE FILE SUMMARIES:\n###\n{{ summary_points }}\n###\n\nThe label best describing this change:\n"), commit_summary: Some("You are an expert programmer, and you are trying to summarize a pull request.\nYou went over every file that was changed in it.\nFor some of these files changes were too big and were omitted in the files diff summary.\nPlease summarize the pull request.\nWrite your response in bullet points, using the imperative tense following the pull request style guide.\nStarting each bullet point with a `-`.\nWrite a high level description. Do not repeat the commit summaries or the file summaries.\nWrite the most important bullet points. The list should not be more than a few bullet points.\n\nTHE FILE SUMMARIES:\n###\n{{ summary_points }}\n###\n\nRemember to write only the most important points and do not write more than a few bullet points.\nTHE PULL REQUEST SUMMARY:\n\n"), commit_title: Some("You are an expert programmer, and you are trying to title a pull request.\nYou went over every file that was changed in it.\nFor some of these files changes were too big and were omitted in the files diff summary.\nPlease summarize the pull request into a single specific theme.\nWrite your response using the imperative tense following the kernel git commit style guide.\nWrite a high level title.\nDo not repeat the commit summaries or the file summaries.\nDo not list individual changes in the title.\n\nEXAMPLE SUMMARY COMMENTS:\n```\nRaise the amount of returned recordings\nSwitch to internal API for completions\nLower numeric tolerance for test files\nSchedule all GitHub actions on all OSs\n```\n\nTHE FILE SUMMARIES:\n###\n{{ summary_points }}\n###\n\nRemember to write only one line, no more than 50 characters.\nTHE PULL REQUEST TITLE:\n"), file_diff: Some("You are an expert programmer, and you are trying to summarize a git diff.\nReminders about the git diff format:\nFor every file, there are a few metadata lines, like (for example):\n```\ndiff --git a/lib/index.js b/lib/index.js\nindex aadf691..bfef603 100644\n--- a/lib/index.js\n+++ b/lib/index.js\n```\nThis means that `lib/index.js` was modified in this commit. Note that this is only an example.\nThen there is a specifier of the lines that were modified.\nA line starting with `+` means it was added.\nA line that starting with `-` means that line was deleted.\nA line that starts with neither `+` nor `-` is code given for context and better understanding.\nIt is not part of the diff.\nAfter the git diff of the first file, there will be an empty line, and then the git diff of the next file.\n\nDo not include the file name as another part of the comment.\nDo not use the characters `[` or `]` in the summary.\nWrite every summary comment in a new line.\nComments should be in a bullet point list, each line starting with a `-`.\nThe summary should not include comments copied from the code.\nThe output should be easily readable. When in doubt, write less comments and not more. Do not output comments that simply repeat the contents of the file.\nReadability is top priority. Write only the most important comments about the diff.\n\nEXAMPLE SUMMARY COMMENTS:\n###\n- Raise the amount of returned recordings from `10` to `100`\n- Fix a typo in the github action name\n- Move the `octokit` initialization to a separate file\n- Add an OpenAI API for completions\n- Lower numeric tolerance for test files\n- Add 2 tests for the inclusive string split function\n###\nMost commits will have less comments than this examples list.\nThe last comment does not include the file names,\nbecause there were more than two relevant files in the hypothetical commit.\nDo not include parts of the example in your summary.\nIt is given only as an example of appropriate comments.\n\n\nTHE GIT DIFF TO BE SUMMARIZED:\n###\n{{ file_diff }}\n###\n\nTHE SUMMARY:\n\n"), translation: Some("You are a professional programmer and translator, and you are trying to translate a git commit message.\nYou want to ensure that the translation is high level and in line with the programmer's consensus, taking care to keep the formatting intact.\n\nNow, translate the following message into {{ output_language }}.\n\nGIT COMMIT MESSAGE:\n\n###\n{{ commit_message }}\n###\n\nRemember translate all given git commit message.\nTHE TRANSLATION:\n") }), output: Some(OutputSettings { conventional_commit: Some(true), lang: Some("en"), show_per_file_summary: Some(false) }), allow_amend: Some(true), file_ignore: Some(["package-lock.json", "yarn.lock", "pnpm-lock.yaml", "Cargo.lock"]) }
2023-03-27T08:22:20.559Z DEBUG [gptcommit::actions::config] Config subcommand - Settings = Settings { model_provider: Some(OpenAI), openai: Some(OpenAISettings { api_key: Some("my-personal-key"), model: Some("gpt-3.5-turbo"), retries: Some(2) }), prompt: Some(PromptSettings { conventional_commit_prefix: Some("You are an expert programmer, and you are trying to summarize a code change.\nYou went over every file that was changed in it.\nFor some of these files changes where too big and were omitted in the files diff summary.\nDetermine the best label for the commit.\n\nHere are the labels you can choose from:\n\n- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)\n- chore: Updating libraries, copyrights or other repo setting, includes updating dependencies.\n- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, GitHub Actions)\n- docs: Non-code changes, such as fixing typos or adding new documentation\n- feat: a commit of the type feat introduces a new feature to the codebase\n- fix: A commit of the type fix patches a bug in your codebase\n- perf: A code change that improves performance\n- refactor: A code change that neither fixes a bug nor adds a feature\n- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)\n- test: Adding missing tests or correcting existing tests\n\n\nTHE FILE SUMMARIES:\n###\n{{ summary_points }}\n###\n\nThe label best describing this change:\n"), commit_summary: Some("You are an expert programmer, and you are trying to summarize a pull request.\nYou went over every file that was changed in it.\nFor some of these files changes were too big and were omitted in the files diff summary.\nPlease summarize the pull request.\nWrite your response in bullet points, using the imperative tense following the pull request style guide.\nStarting each bullet point with a `-`.\nWrite a high level description. Do not repeat the commit summaries or the file summaries.\nWrite the most important bullet points. The list should not be more than a few bullet points.\n\nTHE FILE SUMMARIES:\n###\n{{ summary_points }}\n###\n\nRemember to write only the most important points and do not write more than a few bullet points.\nTHE PULL REQUEST SUMMARY:\n\n"), commit_title: Some("You are an expert programmer, and you are trying to title a pull request.\nYou went over every file that was changed in it.\nFor some of these files changes were too big and were omitted in the files diff summary.\nPlease summarize the pull request into a single specific theme.\nWrite your response using the imperative tense following the kernel git commit style guide.\nWrite a high level title.\nDo not repeat the commit summaries or the file summaries.\nDo not list individual changes in the title.\n\nEXAMPLE SUMMARY COMMENTS:\n```\nRaise the amount of returned recordings\nSwitch to internal API for completions\nLower numeric tolerance for test files\nSchedule all GitHub actions on all OSs\n```\n\nTHE FILE SUMMARIES:\n###\n{{ summary_points }}\n###\n\nRemember to write only one line, no more than 50 characters.\nTHE PULL REQUEST TITLE:\n"), file_diff: Some("You are an expert programmer, and you are trying to summarize a git diff.\nReminders about the git diff format:\nFor every file, there are a few metadata lines, like (for example):\n```\ndiff --git a/lib/index.js b/lib/index.js\nindex aadf691..bfef603 100644\n--- a/lib/index.js\n+++ b/lib/index.js\n```\nThis means that `lib/index.js` was modified in this commit. Note that this is only an example.\nThen there is a specifier of the lines that were modified.\nA line starting with `+` means it was added.\nA line that starting with `-` means that line was deleted.\nA line that starts with neither `+` nor `-` is code given for context and better understanding.\nIt is not part of the diff.\nAfter the git diff of the first file, there will be an empty line, and then the git diff of the next file.\n\nDo not include the file name as another part of the comment.\nDo not use the characters `[` or `]` in the summary.\nWrite every summary comment in a new line.\nComments should be in a bullet point list, each line starting with a `-`.\nThe summary should not include comments copied from the code.\nThe output should be easily readable. When in doubt, write less comments and not more. Do not output comments that simply repeat the contents of the file.\nReadability is top priority. Write only the most important comments about the diff.\n\nEXAMPLE SUMMARY COMMENTS:\n###\n- Raise the amount of returned recordings from `10` to `100`\n- Fix a typo in the github action name\n- Move the `octokit` initialization to a separate file\n- Add an OpenAI API for completions\n- Lower numeric tolerance for test files\n- Add 2 tests for the inclusive string split function\n###\nMost commits will have less comments than this examples list.\nThe last comment does not include the file names,\nbecause there were more than two relevant files in the hypothetical commit.\nDo not include parts of the example in your summary.\nIt is given only as an example of appropriate comments.\n\n\nTHE GIT DIFF TO BE SUMMARIZED:\n###\n{{ file_diff }}\n###\n\nTHE SUMMARY:\n\n"), translation: Some("You are a professional programmer and translator, and you are trying to translate a git commit message.\nYou want to ensure that the translation is high level and in line with the programmer's consensus, taking care to keep the formatting intact.\n\nNow, translate the following message into {{ output_language }}.\n\nGIT COMMIT MESSAGE:\n\n###\n{{ commit_message }}\n###\n\nRemember translate all given git commit message.\nTHE TRANSLATION:\n") }), output: Some(OutputSettings { conventional_commit: Some(true), lang: Some("en"), show_per_file_summary: Some(false) }), allow_amend: Some(true), file_ignore: Some(["package-lock.json", "yarn.lock", "pnpm-lock.yaml", "Cargo.lock"]) }
2023-03-27T08:22:20.559Z DEBUG [gptcommit::settings] Using home dir at /Users/Bobot
2023-03-27T08:22:20.559Z DEBUG [gptcommit::settings] Found config dir at /Users/Bobot/.config/gptcommit
2023-03-27T08:22:20.559Z DEBUG [gptcommit::settings] Applying config file at /Users/Bobot/.config/gptcommit/config.toml
2023-03-27T08:22:20.566Z INFO  [gptcommit::git] Repo path from git: Output { status: ExitStatus(unix_wait_status(0)), stdout: "/Users/Bobot/Repositories/xvautomator\n.git/hooks\n", stderr: "" }
2023-03-27T08:22:20.566Z INFO  [gptcommit::git] Creating dir at .git/hooks
2023-03-27T08:22:20.566Z DEBUG [gptcommit::settings] Applying config from  GPTCOMMIT__*: Ok({"openai_api_base": Value { origin: Some("the environment"), kind: String("XXXXXXXXX") }})
openai.api_base = XXXXXXXXX
Config saved to /Users/Bobot/.config/gptcommit/config.toml

mkdir tmp
cd tmp
git init
rm -rf .git/hooks
gptcommit install