diff options
| author | soryu <soryu@soryu.co> | 2026-02-17 01:57:04 +0000 |
|---|---|---|
| committer | soryu <soryu@soryu.co> | 2026-02-17 01:57:04 +0000 |
| commit | 0f403e44aa0be23acbcccb767870dbaf13474166 (patch) | |
| tree | e0d45bf0085271edbcbbf2000ccf110c79b577c1 | |
| parent | 4bd40f047a6f4703945c6db2811d8feda27241d6 (diff) | |
| download | soryu-0f403e44aa0be23acbcccb767870dbaf13474166.tar.gz soryu-0f403e44aa0be23acbcccb767870dbaf13474166.zip | |
feat: soryu-co/soryu: Generate PR titles from step content instead of directive titlemakima/soryu-co-soryu--generate-pr-titles-from-step-conte-1c4fa4b0
| -rw-r--r-- | makima/src/orchestration/directive.rs | 31 |
1 files changed, 25 insertions, 6 deletions
diff --git a/makima/src/orchestration/directive.rs b/makima/src/orchestration/directive.rs index 62f15d9..09b9861 100644 --- a/makima/src/orchestration/directive.rs +++ b/makima/src/orchestration/directive.rs @@ -1373,9 +1373,16 @@ git checkout -b "$NEW_BRANCH" origin/{base_branch} git push -u origin "$NEW_BRANCH" ``` -3. Create a new PR: +3. Generate a descriptive PR title and create a new PR: + +Based on the steps completed above, generate a descriptive PR title that summarizes the actual changes (not just the directive name "{title}"). The title should: +- Be concise (under 72 characters) +- Describe WHAT was done, not just the project name +- Use conventional commit style if appropriate (feat:, fix:, refactor:, etc.) + +Then create the PR: ``` -gh pr create --title "{title}" --body "{pr_body}" --head "$NEW_BRANCH" --base {base_branch} +gh pr create --title "<YOUR_GENERATED_TITLE>" --body "{pr_body}" --head "$NEW_BRANCH" --base {base_branch} ``` 4. Store the new PR URL: @@ -1437,9 +1444,15 @@ git checkout -b {directive_branch} origin/{base_branch} git push -u origin {directive_branch} ``` -Then create the PR: +Then generate a descriptive PR title and create the PR: + +Based on the steps completed above, generate a descriptive PR title that summarizes the actual changes (not just the directive name "{title}"). The title should: +- Be concise (under 72 characters) +- Describe WHAT was done, not just the project name +- Use conventional commit style if appropriate (feat:, fix:, refactor:, etc.) + ``` -gh pr create --title "{title}" --body "{pr_body}" --head {directive_branch} --base {base_branch} +gh pr create --title "<YOUR_GENERATED_TITLE>" --body "{pr_body}" --head {directive_branch} --base {base_branch} ``` IMPORTANT: After creating the PR, you MUST store the PR URL so the directive system can track it. @@ -1500,9 +1513,15 @@ Done — the PR already exists. git ls-remote --heads origin {pr_branch} ``` -4. If the branch exists, create the PR: +4. If the branch exists, generate a descriptive PR title and create the PR: + +Based on the branch name and directive "{title}", generate a descriptive PR title that summarizes the actual changes. The title should: +- Be concise (under 72 characters) +- Describe WHAT was done, not just the project name +- Use conventional commit style if appropriate (feat:, fix:, refactor:, etc.) + ``` -gh pr create --title "{title}" --body "Directive PR verification — auto-created" --head {pr_branch} --base {base_branch} +gh pr create --title "<YOUR_GENERATED_TITLE>" --body "Directive PR verification — auto-created" --head {pr_branch} --base {base_branch} ``` Then store the resulting URL: ``` |
