git-gpt 0.0.2 → 0.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/Gemfile.lock +3 -2
- data/README.md +6 -0
- data/git-gpt.gemspec +1 -0
- data/lib/git/gpt/version.rb +1 -1
- data/lib/git/gpt.rb +1 -0
- metadata +15 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: a6e17d107e9e41f2ee00f0c9011b6e01e9bc08b9363118420e33d6059a70c15f
|
|
4
|
+
data.tar.gz: 03c1875348e3e9d754737092ac7d6baaee250d9a024c36207ff5feaf5f9af934
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 96a4b1c28c6a1cf5134f9d4ed98007ff20bae6fa23b47cb4222954ab20b90b0b93e8900ff73042293ed38f9e80b37a4d9a6682153db62346cdd612504bc91dac
|
|
7
|
+
data.tar.gz: 876b48b487e4fc603dc79095d8c6186567cdc758bab8b72c5682d4068b52997849306263c14c7a2e0655f1ef30009ac7a533765a26974665854bc73a32d840a7
|
data/Gemfile.lock
CHANGED
|
@@ -1,7 +1,8 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
git-gpt (0.0.
|
|
4
|
+
git-gpt (0.0.3)
|
|
5
|
+
json
|
|
5
6
|
ruby-openai (~> 4.0)
|
|
6
7
|
|
|
7
8
|
GEM
|
|
@@ -9,7 +10,7 @@ GEM
|
|
|
9
10
|
specs:
|
|
10
11
|
ast (2.4.2)
|
|
11
12
|
diff-lcs (1.5.0)
|
|
12
|
-
faraday (2.7.
|
|
13
|
+
faraday (2.7.6)
|
|
13
14
|
faraday-net_http (>= 2.0, < 3.1)
|
|
14
15
|
ruby2_keywords (>= 0.0.4)
|
|
15
16
|
faraday-multipart (1.0.4)
|
data/README.md
CHANGED
|
@@ -31,6 +31,12 @@ git gpt file1 file2 file3
|
|
|
31
31
|
|
|
32
32
|
In the above example, `file1`, `file2`, and `file3` are placeholders for the file names you want to focus on. This will generate a commit message based on the changes in those files only.
|
|
33
33
|
|
|
34
|
+
### USAGE NOTE
|
|
35
|
+
|
|
36
|
+
`git gpt` does not actually commit your code, it simply prints a commit message that you can choose to use or not. If you run it multiple times, you will likely get different results.
|
|
37
|
+
|
|
38
|
+
By default it asks ChatGPT to create short messages. If you like longer or multiline messages, you can adjust your prompt (see Advanced Configuration below).
|
|
39
|
+
|
|
34
40
|
## Basic Configuration
|
|
35
41
|
|
|
36
42
|
Best practice is to set the `OPENAI_API_KEY` environment veriable. Optionally, you can set `OPENAI_ORGANIZATION_ID`.
|
data/git-gpt.gemspec
CHANGED
|
@@ -35,6 +35,7 @@ Gem::Specification.new do |spec|
|
|
|
35
35
|
# Uncomment to register a new dependency of your gem
|
|
36
36
|
# spec.add_development_dependency "rspec"
|
|
37
37
|
# spec.add_dependency "thor"
|
|
38
|
+
spec.add_dependency "json"
|
|
38
39
|
spec.add_dependency "ruby-openai", "~> 4.0"
|
|
39
40
|
|
|
40
41
|
# For more information and examples about making a new gem, check out our
|
data/lib/git/gpt/version.rb
CHANGED
data/lib/git/gpt.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: git-gpt
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.0.
|
|
4
|
+
version: 0.0.4
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Chris Petersen
|
|
@@ -10,6 +10,20 @@ bindir: exe
|
|
|
10
10
|
cert_chain: []
|
|
11
11
|
date: 2023-06-08 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
|
+
- !ruby/object:Gem::Dependency
|
|
14
|
+
name: json
|
|
15
|
+
requirement: !ruby/object:Gem::Requirement
|
|
16
|
+
requirements:
|
|
17
|
+
- - ">="
|
|
18
|
+
- !ruby/object:Gem::Version
|
|
19
|
+
version: '0'
|
|
20
|
+
type: :runtime
|
|
21
|
+
prerelease: false
|
|
22
|
+
version_requirements: !ruby/object:Gem::Requirement
|
|
23
|
+
requirements:
|
|
24
|
+
- - ">="
|
|
25
|
+
- !ruby/object:Gem::Version
|
|
26
|
+
version: '0'
|
|
13
27
|
- !ruby/object:Gem::Dependency
|
|
14
28
|
name: ruby-openai
|
|
15
29
|
requirement: !ruby/object:Gem::Requirement
|