Skip to content

Conversation

@nathro
Copy link
Collaborator

@nathro nathro commented Aug 11, 2025

Add optional model selection for PR description generation

  • Add a new optional model input to the action. This value is passed through to augmentcode/augment-agent to choose the LLM used for generation (e.g., gpt-4o, claude-3-5-sonnet). When omitted, the agent’s default model is used.
  • Document the model input in the README inputs table with examples.
  • Update the augmentcode/augment-agent reference from a pinned commit to the @v0 tag to track the latest minor updates of the agent.

Impact

  • No breaking changes; existing workflows continue to work without modification.
  • Provides teams control over quality/cost/provider by selecting a model.
  • If strict reproducibility is needed, consider pinning a specific agent commit.

🤖 This description was generated automatically. Please react with 👍 if it's helpful or 👎 if it needs improvement.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding the configurable model input and updating the action reference. I left two small, high-confidence suggestions focused on security and docs clarity.

uses: augmentcode/augment-agent@6f08f56902d6728a0ffbbb2004c136c06fec8104 # v0.1.0
uses: augmentcode/augment-agent@v0
with:
augment_session_auth: ${{ inputs.augment_session_auth }}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using a mutable tag (@v0) makes the workflow susceptible to supply‑chain issues if the tag is moved. Consider pinning to an immutable commit SHA and keeping a comment for readability, for example:

uses: augmentcode/augment-agent@<commit_sha> # v0

This preserves security while still signaling the intended major/minor version.

| `repo_name` | The full name (owner/repo) of the repository | Yes | `${{ github.repository }}` |
| `custom_guidelines` | Custom guidelines for PR descriptions (optional) | No | See [Custom Guidelines](#custom-guidelines) section |
| `model` | Optional model to use for generation | No | e.g. `gpt-4o`, `claude-3-5-sonnet`, etc. |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice addition. To improve discoverability, consider adding a quick usage example that shows how to set model in the workflow, e.g. in one of the examples:

with:
  # ...existing inputs
  model: gpt-4o

This helps users understand exactly where/how to pass the new input.

README.md Outdated
| `pull_number` | The number of the pull request being described | Yes | `${{ github.event.pull_request.number }}` |
| `repo_name` | The full name (owner/repo) of the repository | Yes | `${{ github.repository }}` |
| `custom_guidelines` | Custom guidelines for PR descriptions (optional) | No | See [Custom Guidelines](#custom-guidelines) section |
| `model` | Optional model to use for generation | No | e.g. `gpt-4o`, `claude-3-5-sonnet`, etc. |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The example should probably be a model that's publicly available (sonnet4 or gpt5)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, I forgot to check this. Will update.

@nathro nathro merged commit 4117e9e into main Aug 11, 2025
1 check passed
@nathro nathro deleted the add_model_support branch August 11, 2025 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants