guettli/sharedinbox
1
0
Fork 0
Code Issues 21 Pull Requests 6 Actions Packages Projects Releases Wiki Activity

Duplicated CI runs? #483

New Issue
Closed
opened 2026-06-06 15:05:02 +00:00 by guettli · 2 comments
guettli commented 2026-06-06 15:05:02 +00:00 (Migrated from codeberg.org)
Copy Link
Copy Source

I see duplicated CI runs?

https://codeberg.org/guettli/sharedinbox/actions

Why?

How to fix?

I see duplicated CI runs? https://codeberg.org/guettli/sharedinbox/actions Why? How to fix?
guettlibot commented 2026-06-06 15:10:04 +00:00 (Migrated from codeberg.org)
Copy Link
Copy Source

The root cause is clear. Here's the plan:

Root cause: .forgejo/workflows/ci.yml line 2 uses on: [push, pull_request]. When a commit is pushed to a feature branch that has an open pull request, Forgejo fires both a push event and a pull_request event — resulting in two identical CI runs for every PR update.

Fix: Scope the push trigger to the main branch only. PRs will still trigger via pull_request; direct pushes to main (merges) will trigger via push. The two events will never fire together for the same commit.

Change required — .forgejo/workflows/ci.yml:

# Before
on: [push, pull_request]

# After
on:
  push:
    branches:
      - main
  pull_request:

That one change eliminates the duplicate. No other workflow files are affected:

  • deploy.yml and chaos-monkey.yml use schedule/workflow_dispatch only — no duplicate risk.
  • website.yml already correctly scopes its push trigger to branches: [main].
  • renovate.yml, windows-nightly.yml, firebase-tests.yml would need to be checked for the same pattern, but ci.yml is the reported source.
The root cause is clear. Here's the plan: --- **Root cause**: `.forgejo/workflows/ci.yml` line 2 uses `on: [push, pull_request]`. When a commit is pushed to a feature branch that has an open pull request, Forgejo fires **both** a `push` event and a `pull_request` event — resulting in two identical CI runs for every PR update. **Fix**: Scope the `push` trigger to the `main` branch only. PRs will still trigger via `pull_request`; direct pushes to `main` (merges) will trigger via `push`. The two events will never fire together for the same commit. **Change required** — `.forgejo/workflows/ci.yml`: ```yaml # Before on: [push, pull_request] # After on: push: branches: - main pull_request: ``` That one change eliminates the duplicate. No other workflow files are affected: - `deploy.yml` and `chaos-monkey.yml` use `schedule`/`workflow_dispatch` only — no duplicate risk. - `website.yml` already correctly scopes its `push` trigger to `branches: [main]`. - `renovate.yml`, `windows-nightly.yml`, `firebase-tests.yml` would need to be checked for the same pattern, but `ci.yml` is the reported source.
guettlibot commented 2026-06-06 15:40:04 +00:00 (Migrated from codeberg.org)
Copy Link
Copy Source

Fixed and PR opened: https://codeberg.org/guettli/sharedinbox/pulls/490

What changed: .forgejo/workflows/ci.yml previously used on: [push, pull_request], which fires two CI runs for every commit pushed to a feature branch with an open PR — one for the push event and one for the pull_request event. Scoping the push trigger to branches: [main] means feature-branch commits only trigger via pull_request, while direct pushes to main (merge commits) still trigger via push.

Fixed and PR opened: https://codeberg.org/guettli/sharedinbox/pulls/490 **What changed**: `.forgejo/workflows/ci.yml` previously used `on: [push, pull_request]`, which fires two CI runs for every commit pushed to a feature branch with an open PR — one for the `push` event and one for the `pull_request` event. Scoping the `push` trigger to `branches: [main]` means feature-branch commits only trigger via `pull_request`, while direct pushes to `main` (merge commits) still trigger via `push`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
NeedSupervisor
Issue escalated to a human supervisor; agentloop will skip it until cleared.
 State/InProgress
State/Later
State/Planned
automerge
Eligible for automatic merge by CI
 ci-failure
Issue opened by agentloop to track a failing CI workflow; used for deduplication.
 do-not-merge
Plan PR — review only, do not merge.
 loop/code
Add to run the built-in "code" prompt; override at prompts/code.md.
 loop/code-ci-pending
Prompt "code" finished; waiting for the PR's CI to pass before advancing.
 loop/code-done
Prompt "code" finished successfully.
 loop/code-in-process
Agent for the "code" prompt is currently running on this issue.
 loop/merge
Managed by agentloop
 loop/merge-done
Managed by agentloop
 loop/merge-in-process
Managed by agentloop
 loop/plan
Add to run the built-in "plan" prompt; override at prompts/plan.md.
 loop/plan-done
Prompt "plan" finished successfully.
 loop/plan-in-process
Agent for the "plan" prompt is currently running on this issue.
No labels loop/merge
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
guettlibot guettli
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: guettli/sharedinbox#483