Feature Request: Summarize all commit about gptcommit

[zurawiki]

Based on the multiple diff, can we summarize a sentence for creating Pull Request?

How would you use this in your workflow today?

Also, I think we can add some configurations to ignore some files

We do ignore some files! The default files are at

gptcommit/src/settings.rs

Lines 26 to 31 in 4eccf5a

	static DEFAULT_FILES_TO_IGNORE: &[&str; 4] = &[
	"package-lock.json",
	"yarn.lock",
	"pnpm-lock.yaml",
	"Cargo.lock",
	];

You can configure them per-repo with gptcommit config set file_ignore

[Umiiii]

Based on the multiple diff, can we summarize a sentence for creating Pull Request?

How would you use this in your workflow today?

Also, I think we can add some configurations to ignore some files

We do ignore some files! The default files are at

gptcommit/src/settings.rs

Lines 26 to 31 in 4eccf5a

	static DEFAULT_FILES_TO_IGNORE: &[&str; 4] = &[
	"package-lock.json",
	"yarn.lock",
	"pnpm-lock.yaml",
	"Cargo.lock",
	];

You can configure them per-repo with gptcommit config set file_ignore

Sure!
Suppose you have made several commits in your local workspace, and now you want to submit them as a pull request to be merged into the master branch later. To make the process smoother, it's important to provide a clear and concise summary of the changes you've made. This summary should include the main features or fixes implemented by your commits, as well as any relevant information about the project or the development process. A well-written summary can help the reviewer understand your changes and make the merging process more efficient.

[zurawiki]

Hey @Umiiii , thanks for the feedback. Right now, making summaries across multiple commits is not support as gptcommit is for git commits

[Niek]

This would also be a great feature to support changelog creation.