-
Notifications
You must be signed in to change notification settings - Fork 12
feat: granular PR commits #218
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
base: main
Are you sure you want to change the base?
Conversation
INPUT_SIGNED_COMMITS=false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You okay with this @jagarnica
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some considerations before making these changes. I'm also not sure that its really scope creep to also do the split commits for signed commits -- I would find it confusing on both sides that the action works differently with respect to split commits based on whether commit signing was enabled.
internal/git/git.go
Outdated
}{ | ||
{paths: []string{"**/.speakeasy/", "*gen.yaml", "*gen.lock", "*workflow.yaml", "*workflow.lock"}, msg: "build: Speakeasy config and lock files " + speakeasyVersionSuffix}, | ||
{paths: []string{"*.md"}, msg: "docs: regenerate markdown files " + speakeasyVersionSuffix}, | ||
{paths: []string{"."}, msg: "feat: regenerate SDK " + speakeasyVersionSuffix}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will cause the PR description to be feat: regenerate SDK (v1.234.5)
when it previously was ci: regenerated with Speakeasy CLI 1.234.5
. I personally think the new description is confusing since there are multiple versions with any given SDK:
- SDK/target version
- OpenAPI document version
- Speakeasy version (and even generator version if we're being pedantic about versions)
The target being rebuilt may also not be an SDK. (Terraform and other internal thing I'm working on 😉)
Maybe best to keep it similar to the old message and consider dropping the CLI and version part?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow nice. Great idea
INPUT_SIGNED_COMMITS=false
as it's more commonScreen.Recording.2025-05-07.at.08.27.08.mov