ci: skip queue-verified Dev and Dependencies jobs on pushes to main

[comphead]

Which issue does this PR close?

• Part of Reduce GitHub Actions usage (DataFusion is currently the top ASF consumer of GHA minutes) #25148. This PR does not close the issue.
• Follow-up to ci: skip queue-verified Rust jobs on pushes to main #25365, which did the same for rust.yml. Answers ci: skip queue-verified Rust jobs on pushes to main #25365 (comment).

Rationale for this change

The inflated test count on the main commits page is duplicated checks. Every commit is checked twice at the same SHA, once by the merge queue and once by the push that follows.

The merge_group event is separate from the pull_request and push events.

— Events that trigger workflows

Neither event knows the other ran, so a workflow listing both runs twice. At 3ab72e6 the two Dev runs share a head_sha and differ only in event and ref: 35262885559 (merge_group, gh-readonly-queue/main/pr-25383-98b26c5f9…) and 35263735243 (push, main). Dependencies is the same pair. GET /commits/3ab72e61…/check-runs returns each of these seven names twice:

Check License Header                              Circular Dependency Check
Check Markdown Links                              Detect Unused Dependencies
Spell Check with Typos
Use prettier to check formatting of documents
Validate required_status_checks in .asf.yaml

The existing branches-ignore: 'gh-readonly-queue/**' does not prevent this. It suppresses a third run, the push event on the queue's own temporary branch, not the push to main.

Scale: from September 9 to 17, 2026 each workflow ran 156 times for pushes to main, and all 156 SHAs already had a merge_group run of the same workflow at the same SHA. Over the seven full days September 10 to 16 there were 120 such commits, at 1.81 (Dev) plus 4.69 (Dependencies) mean runner-minutes each, so about 780 runner-minutes per week. All seven jobs report runner_group: "GitHub Actions" and none use Runs-On, so every minute saved comes off the shared GitHub-hosted quota #25148 is about.

Seven other names are also doubled at that SHA. Those are the rust.yml jobs #25365 deliberately kept on main for caches, coverage, and the non-required FFI check. This PR leaves them alone.

What changes are included in this PR?

main is added to the existing branches-ignore list in .github/workflows/dev.yml and .github/workflows/dependencies.yml.

Event	Dev / Dependencies jobs
Push to main	0
Merge group, pull request, push to any other branch	7
workflow_dispatch (Dependencies)	2

Unlike rust.yml, neither workflow has a job worth keeping post-merge: none uses actions/cache or rust-cache, none uploads an artifact or coverage, and all seven are required checks the merge queue already satisfies. With nothing to preserve, excluding the event at the trigger is simpler and cheaper than a per-job if:, since no run is created at all.

Keeping branches-ignore rather than a positive branches: list is deliberate: the merge queue is configured only for main, so release branches have no pre-merge run to inherit and must keep post-push coverage.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.33%. Comparing base (edc936f) to head (6076818).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #25443      +/-   ##
==========================================
- Coverage   82.33%   82.33%   -0.01%     
==========================================
  Files        1137     1137              
  Lines      432498   432498              
  Branches   432498   432498              
==========================================
- Hits       356116   356115       -1     
- Misses      54843    54844       +1     
  Partials    21539    21539              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[alamb]

Let's give it a try!

[alamb]

Thanks @comphead

[comphead]

Less duplicates, but some still exist, would need a followup

[alamb]

Though it looks good to me that it is now explicitly skipping the push checks (as they already ran in the merge_group) 👍

Thanks for this @comphead

[comphead]

it still runs linux tests twice, I'm brainstorming how to dedup it gently, prob would require some CI restructure.