Skip to content

[repo-status] Daily Repo Status β€” May 13, 2026Β #98

@github-actions

Description

@github-actions

🌟 Wednesday Check-In β€” May 13, 2026

Hey @Herm71! The repo is in great shape after last Sunday's v0.5.8 release. With the new global release workflow humming, all that's standing between you and a clean backlog is one well-scoped PR. Let's go! πŸ’ͺ


πŸ“Š Repository Snapshot

Metric Value
Latest release βœ… v0.5.8 β€” May 11, 2026
Open PRs 1 β€” PR #21 (Draft Β· Copilot-authored)
Open real bugs 1 β€” Issue #3 double-save on Fund type change
Last commit to main May 11, 2026 β€” chore(release): 0.5.8 by @Herm71
Total open issues 32 (31 are daily-status reports)

πŸš€ Recent Activity

v0.5.8 shipped on May 11 with one key improvement:

  • βš™οΈ PR #96 merged β€” Release workflow migrated to UCSC's org-wide global GitHub Actions. Includes dry-run trigger support, composer.json metadata (name, description, license) required for validation, and stable ZIP artifact naming.
  • πŸ“¦ Release asset ucsc-giving-functionality-plugin.zip (37 KB) auto-published and already downloaded once!

No commits since the release β€” the branch is clean and ready for the next merge. 🧹


πŸ” The One Thing Left: PR #21

Fix: Double-Save on Fund Type Change Β· Closes Issue #3 (open since March 2025 β€” over a year!)

This Copilot-authored fix is clean, surgical, and well-understood:

Detail Value
Status 🟑 Draft Β· No conflicts βœ…
File changed lib/functions/general.php only
Net change +43 / βˆ’18 lines
Open since March 3, 2026 (~71 days)

What the fix does:

  • Adds ucscgiving_sync_fund_type_term() hooked to rest_after_insert_fund at priority 999, firing after WordPress's handle_terms() overwrites the taxonomy β€” re-syncing fund-type to the correctly saved fund-type-term meta value
  • Switches ucscgiving_link_filter() to wp_get_post_terms() for a live DB read, bypassing ACF's stale cache

πŸ‘‰ Test on staging β†’ un-draft β†’ merge β†’ close this year-old bug for good! A clean v0.5.9 follows naturally. πŸ†


βœ… Actionable Next Steps

  1. πŸ”€ Advance PR #21 β€” With the shiny new global release workflow in place, this is the perfect time to test the double-save fix on staging, un-draft, and merge.
  2. πŸš€ Tag v0.5.9 β€” Once PR #21 merges, run npm run release for a focused single-fix patch release.
  3. πŸ—‚οΈ Bulk-close old status issues β€” ~31 daily-status report issues are still open; closing them will give the issue tracker back its focus on real work items.

gh-aw-workflow-call-id: ucsc/ucsc-giving-functionality/daily-repo-status

πŸ€– Auto-generated by the daily-repo-status workflow on May 13, 2026.

Generated by Daily Repo Status Β· β—·

Generated by Daily Repo Status Β· β—·

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/daily-repo-status.md@9646d0870492f62bd9a67b4d38ddfbb731f7e0a4

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions