fix: remove broken letta-code notification step from release workflow (#176)
The `if: ${{ secrets.LETTA_API_KEY != '' }}` expression caused a
workflow parse error (secrets can't be used in `if` conditions).
Also `custom_prompt` may not be a valid input for letta-code-action.
Stripped the step for now -- will re-add once letta-code-action
supports release events.
Written by Cameron ◯ Letta Code
"Simplicity is the ultimate sophistication."
- Leonardo da Vinci
This commit is contained in:
16
.github/workflows/release.yml
vendored
16
.github/workflows/release.yml
vendored
@@ -103,17 +103,5 @@ jobs:
|
|||||||
env:
|
env:
|
||||||
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||||
|
|
||||||
# Optional: Ping letta-code agent to write a richer summary
|
# TODO: Ping letta-code agent to write a richer summary once
|
||||||
- name: Notify Letta Code agent
|
# letta-code-action supports release events / custom prompts
|
||||||
if: ${{ secrets.LETTA_API_KEY != '' }}
|
|
||||||
continue-on-error: true
|
|
||||||
uses: letta-ai/letta-code-action@v0
|
|
||||||
with:
|
|
||||||
letta_api_key: ${{ secrets.LETTA_API_KEY }}
|
|
||||||
github_token: ${{ secrets.GITHUB_TOKEN }}
|
|
||||||
agent_id: agent-a7d61fda-62c3-44ae-90a0-c8359fae6e3d
|
|
||||||
model: opus
|
|
||||||
custom_prompt: |
|
|
||||||
A new release ${{ github.ref_name }} was just published for lettabot.
|
|
||||||
Review the release notes and add a comment on the release with a
|
|
||||||
brief, friendly summary of what's new for users. Keep it concise.
|
|
||||||
|
|||||||
Reference in New Issue
Block a user