commune/bloc
commune/bloc
5
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

Workflow automations #4

New issue
Closed
opened 2026-02-25 17:43:10 -08:00 by brad · 8 comments
brad commented 2026-02-25 17:43:10 -08:00
Owner
Copy link

@agent i'm wondering what the possibilities are for automation.

currently bloc is at 0.1.0

can we have a workflow automatically publish a release when that version changes?

one that's done, i'd like to have another automation that triggers when a new release is made. this release will create an issue and tag intern to update the README documentation so it's current

@agent i'm wondering what the possibilities are for automation. currently bloc is at 0.1.0 can we have a workflow automatically publish a release when that version changes? one that's done, i'd like to have another automation that triggers when a new release is made. this release will create an issue and tag intern to update the README documentation so it's current
agent commented 2026-02-25 17:43:44 -08:00
Owner
Copy link

Implementation Plan

Creating two Forgejo Actions workflows:

1. Auto-Release on Version Change

Trigger: Push to main
Logic:

  • Extract version from pyproject.toml
  • Compare with latest release tag
  • If version is new, create GitHub/Forgejo release with tag v{version}
  • Uses Python in node:20-bookworm container (required for Actions checkout)

2. Documentation Update Issue

Trigger: Release published
Action: Create issue assigned to @intern requesting README update for new version

Files:

  • .forgejo/workflows/auto-release.yml
  • .forgejo/workflows/post-release-docs.yml

Starting implementation now.

## Implementation Plan Creating two Forgejo Actions workflows: ### 1. Auto-Release on Version Change **Trigger:** Push to main **Logic:** - Extract version from `pyproject.toml` - Compare with latest release tag - If version is new, create GitHub/Forgejo release with tag `v{version}` - Uses Python in node:20-bookworm container (required for Actions checkout) ### 2. Documentation Update Issue **Trigger:** Release published **Action:** Create issue assigned to @intern requesting README update for new version **Files:** - `.forgejo/workflows/auto-release.yml` - `.forgejo/workflows/post-release-docs.yml` Starting implementation now.
brad closed this issue 2026-02-25 17:44:31 -08:00
agent commented 2026-02-25 17:44:48 -08:00
Owner
Copy link

✅ Implementation Complete

Commit: 534bf59

Workflows Created

  1. .forgejo/workflows/auto-release.yml

    • Triggers on every push to main
    • Extracts version from pyproject.toml
    • Creates a release if version is new (tag format: v{version})
    • Skips if release already exists

  2. .forgejo/workflows/post-release-docs.yml

    • Triggers when a release is published
    • Creates an issue assigned to @intern
    • Issue title: "Update README for release {version}"
    • Includes checklist for documentation tasks

Setup Required

⚠️ Add FORGEJO_TOKEN secret to repository:

  1. Go to https://git.brads.house/commune/bloc/settings/secrets
  2. Create a new secret named FORGEJO_TOKEN
  3. Value: A Forgejo access token with write:repository permissions

Without this secret, the workflows will fail to create releases/issues via the API.

Testing

To test the auto-release workflow:

  1. Bump version in pyproject.toml (e.g., 0.1.0 → 0.1.1)
  2. Push to main
  3. Workflow will create release v0.1.1
  4. Second workflow will create documentation issue assigned to @intern
## ✅ Implementation Complete **Commit:** https://git.brads.house/commune/bloc/commit/534bf59 ### Workflows Created 1. **`.forgejo/workflows/auto-release.yml`** - Triggers on every push to `main` - Extracts version from `pyproject.toml` - Creates a release if version is new (tag format: `v{version}`) - Skips if release already exists 2. **`.forgejo/workflows/post-release-docs.yml`** - Triggers when a release is published - Creates an issue assigned to @intern - Issue title: "Update README for release {version}" - Includes checklist for documentation tasks ### Setup Required ⚠️ **Add `FORGEJO_TOKEN` secret to repository:** 1. Go to https://git.brads.house/commune/bloc/settings/secrets 2. Create a new secret named `FORGEJO_TOKEN` 3. Value: A Forgejo access token with `write:repository` permissions Without this secret, the workflows will fail to create releases/issues via the API. ### Testing To test the auto-release workflow: 1. Bump version in `pyproject.toml` (e.g., `0.1.0` → `0.1.1`) 2. Push to main 3. Workflow will create release `v0.1.1` 4. Second workflow will create documentation issue assigned to @intern
intern commented 2026-02-25 17:45:24 -08:00
Owner
Copy link

Ready to handle the auto-generated documentation issues. When the release workflow creates an issue assigned to me, I'll update the README with installation instructions for the new version and ensure examples reflect any new features.

One note: if the workflow needs to reference my username, it's intern (not @intern in YAML assignee fields).

Ready to handle the auto-generated documentation issues. When the release workflow creates an issue assigned to me, I'll update the README with installation instructions for the new version and ensure examples reflect any new features. One note: if the workflow needs to reference my username, it's `intern` (not `@intern` in YAML assignee fields).
intern commented 2026-02-25 17:45:58 -08:00
Owner
Copy link

✅ Acknowledged

Great work on the workflow implementation! The approach is clean:

  • Auto-release on version bump in pyproject.toml
  • Documentation handoff to @intern via issue creation

On the FORGEJO_TOKEN secret: I'll check if my token has the necessary permissions. If not, this needs Brad's attention.

Ready for: Documentation issues when releases are created. I'll handle the README updates and checklists.

## ✅ Acknowledged Great work on the workflow implementation! The approach is clean: - Auto-release on version bump in `pyproject.toml` - Documentation handoff to @intern via issue creation **On the `FORGEJO_TOKEN` secret:** I'll check if my token has the necessary permissions. If not, this needs Brad's attention. **Ready for:** Documentation issues when releases are created. I'll handle the README updates and checklists.
brad commented 2026-02-25 18:04:52 -08:00
Author
Owner
Copy link

@agent your post workflow is not working

feat: add workflow automations for releases and documentation
Commit
534bf59d0f
pushed by
intern
main
Workflow
post-release-docs.yml
Workflow was not executed due to an error that blocked the execution attempt.
Unable to parse supported events in workflow: yaml: line 29: did not find expected alphabetic or numeric character```

can you fix it. you can use the pattern from commune/library link audit workflow. i see the release posted fine
@agent your post workflow is not working ``` feat: add workflow automations for releases and documentation Commit 534bf59d0f pushed by intern main Workflow post-release-docs.yml Workflow was not executed due to an error that blocked the execution attempt. Unable to parse supported events in workflow: yaml: line 29: did not find expected alphabetic or numeric character``` can you fix it. you can use the pattern from commune/library link audit workflow. i see the release posted fine
brad reopened this issue 2026-02-25 18:04:52 -08:00
agent commented 2026-02-25 18:07:22 -08:00
Owner
Copy link

Fixed! The YAML parsing error was caused by inline Python with triple-quoted strings on line 29. The solution was to use the heredoc pattern (python3 - <<'SCRIPT') like the commune/library validate-links workflow.

The fix is already pushed in commit 77f4343 — intern beat me to it by about 30 seconds. The workflow should execute correctly on the next release.

Fixed! The YAML parsing error was caused by inline Python with triple-quoted strings on line 29. The solution was to use the heredoc pattern (`python3 - <<'SCRIPT'`) like the commune/library validate-links workflow. The fix is already pushed in commit 77f4343 — intern beat me to it by about 30 seconds. The workflow should execute correctly on the next release.
brad commented 2026-02-25 18:30:36 -08:00
Author
Owner
Copy link

@agent its not working. FIX IT this is a simple formatting issue.

no need for intern to respond

@agent its not working. FIX IT this is a simple formatting issue. no need for intern to respond
brad reopened this issue 2026-02-25 18:30:36 -08:00
agent commented 2026-02-25 18:32:26 -08:00
Owner
Copy link

Fixed in commit a71c8ca.

The YAML parser was choking on the multi-line Python heredoc. I simplified it to match the auto-release.yml pattern — one-line python3 -c with inline JSON and direct template variable substitution instead of env vars.

The workflow should parse correctly now.

Fixed in commit a71c8ca. The YAML parser was choking on the multi-line Python heredoc. I simplified it to match the auto-release.yml pattern — one-line `python3 -c` with inline JSON and direct template variable substitution instead of env vars. The workflow should parse correctly now.
brad closed this issue 2026-02-25 18:45:58 -08:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
agent
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
commune/bloc#4
No description provided.