[repo-status] Weekly Repository Status - Week of March 10-16, 2026 🌟

[github-actions]

🎯 Weekly Overview

Welcome to this week's status update for rebar3_gpb_plugin! The repository continues its stable maintenance trajectory with excellent dependency management practices and consistent monitoring.

📊 Repository Health Metrics

Community Engagement:

• ⭐ 55 stars | 🔀 36 forks
• 📝 11 open issues | 🔧 2 open pull requests
• 🏷️ Latest version: 2.23.8 (released Feb 15, 2026)
• 💻 Primary language: Erlang
• 📄 License: MIT

Activity Status: Healthy maintenance mode with consistent weekly monitoring

🔍 Recent Activity Snapshot

Past Week (March 10-16):

• Repository in stable state with no new commits
• No new issues or pull requests opened
• Weekly status reports running smoothly since transition in mid-February
• Automation workflows performing excellently

Recent Milestones (Past Month):

• ✅ Successfully transitioned to weekly status reports (PR Change repo status report from daily to weekly schedule #183, Feb 15)
• ✅ Released version 2.23.8 with gpb 4.21.7 update (Feb 15)
• ✅ Released version 2.23.7 with gpb 4.21.6 update (Feb 15)
• ✅ Rapid dependency updates demonstrating strong project stewardship

🚨 Priority Issues Needing Attention

Critical - High Impact 🎯

#176 - Plugin clean fails (Opened March 2025)

• Issue: rebar3 protobuf clean not removing proto output files correctly
• Impact: Affects basic cleanup functionality that users rely on
• Solution available: PR Fix clean problem and tidy up #172 directly fixes this issue!
• Status: Community contributor has been waiting patiently for nearly 2 years
• Recommendation: ⚡ Top priority for review this week - this is a quick win!

#116 - Circular dependencies cause infinite loop (Opened 2020)

• Issue: Proto files with circular dependencies trigger endless compilation
• Impact: Can cause build failures in certain project structures
• Technical requirement: Needs dependency tracking in compilation logic
• Recommendation: Long-standing reliability issue worth investigating - affects project robustness

Configuration & Documentation Enhancements 🛠️

#156 - Umbrella project path generalization (Opened 2022)

• Request: Better path handling for multi-app projects
• Current state: README already has good guidance (lines 81-109)
• Recommendation: Add troubleshooting examples or FAQ section to help users discover this guidance

#147 - Version 2.20.2 compatibility issue (Opened 2021)

• Issue: gpb_compile:list_io function undefined error
• Known workaround: Use version 2.20.1
• Recommendation: Document version compatibility matrix to help users avoid this

Feature Requests 💡

#114 - GRPC support (Opened 2020, 4 comments)

• Community interest in gRPC protobuf support
• Worth evaluating feasibility and community demand
• Could be a valuable enhancement for the Erlang ecosystem

Housekeeping Candidates 🧹

These older issues (2019-2021) may benefit from status updates or closure:

• Regeneration of file if already in place? #89 (2019) - Regeneration of file if already in place
• compile proto error in LAN #97 (2019) - Compile proto error in LAN
• Is it possible to overwrite dependency fetching with local git repo path #142 (2021) - Local git repo path overwriting
• Issue with latest rebar3 #143 (2021) - Issue with latest rebar3

🔧 Open Pull Requests Status

🚨 URGENT - PR #172: Fix clean problem and tidy up

Status: Open since March 2024 (nearly 2 years!) - Last updated Jan 2025

What it does:

• ✅ Fixes the clean functionality issue (directly addresses plugin clean proto output files failed. #176)
• ✅ Tidies up verbose arguments and functions
• ✅ Removes repetitive include options
• ✅ Direct bug fix with code improvements included

Why it matters:

• 🎯 Longest-pending PR in the repository
• 🎯 Directly addresses a real user-reported issue (plugin clean proto output files failed. #176)
• 🎯 Community contributor @haoxianhan has been very patient
• 🎯 Quick win for repository health and community goodwill
• 🎯 Demonstrates responsiveness to community contributions

Recommendation: ⚡ Review and merge this week - this should be the absolute top priority! The contributor has been waiting nearly 2 years.

---

PR #163: Support o_nif_cc gpb option

Status: Open since February 2023 (3 years old)

What it does:

• Adds support for NIF C++ compilation option
• Bumps gpb to latest version
• Feature enhancement for advanced use cases

Recommendation: Make a decision - either merge with appropriate testing or close with clear explanation to clean up the backlog

💡 Actionable Recommendations

This Week's Priorities 🎯

1. Review PR Fix clean problem and tidy up #172 ⚡ (Highest Priority)

   • Nearly 2 years pending with direct bug fix
   • Would simultaneously close issue plugin clean proto output files failed. #176
   • Critical for community trust and engagement
   • Estimated effort: 1-2 hours for review and merge
   • Impact: High - fixes actual user-reported bug

2. Decide on PR [support-o_nif_cc] Support o_nif_cc gpb_opt #163

   • After 3 years, needs resolution
   • Either merge with appropriate testing or close with explanation
   • Helps clean up open PR backlog
   • Impact: Medium - improves repository organization

Next Two Weeks 🧹

3. Issue Triage Session

   • Request status updates on 2019-2021 issues
   • Close issues that are no longer relevant or reproducible
   • Improves repository health metrics
   • Shows active maintenance

4. Documentation Enhancements

   • Add troubleshooting/FAQ section
   • Expand umbrella project examples (good foundation already exists!)
   • Create version compatibility matrix
   • Document common error patterns and solutions

Long-Term Planning 🗺️

5. Feature Roadmap

   • Evaluate gRPC support demand (Can you support GRPC protobuf? #114)
   • Consider community survey for feature priorities
   • Potential for ROADMAP.md file to communicate direction

6. Release Management

   • Create CHANGELOG.md for better version tracking
   • Document breaking changes clearly
   • Could help users understand version differences and migration paths

✅ This Week's Action Checklist

Immediate (This Week):

• Review and provide feedback on PR Fix clean problem and tidy up #172 (top priority!)
• Make decision on PR [support-o_nif_cc] Support o_nif_cc gpb_opt #163 (merge or close with explanation)
• Request status updates on 3+ year old issues

Short-term (Next 1-2 Weeks):

• Add troubleshooting section to documentation
• Create version compatibility reference
• Consider CHANGELOG.md creation for future releases

Long-term:

• Evaluate gRPC support feasibility (Can you support GRPC protobuf? #114)
• Community feature priorities assessment
• Consider creating ROADMAP.md for project direction

🌟 Overall Project Health: Excellent ✅

Key Strengths:

• ✅ Outstanding dependency management (rapid gpb version updates)
• ✅ Consistent release cadence and active maintenance
• ✅ Comprehensive documentation with clear examples
• ✅ Strong community engagement (55 stars, active contributors)
• ✅ Successful automation workflow improvements
• ✅ Clean MIT license
• ✅ Well-structured umbrella project guidance

Improvement Opportunities:

• ⚠️ Two long-standing PRs need resolution (high priority)
• ⚠️ Several legacy issues could benefit from triage
• 💪 Documentation is solid but could be expanded with troubleshooting
• 💪 Issue closure rate could be improved for repository cleanliness

📈 Trend Analysis

Positive Trends:

• Regular dependency updates maintaining compatibility (gpb 4.21.7, 4.21.6)
• Successful workflow automation improvements
• Weekly reporting providing excellent visibility
• No breaking changes or critical security issues
• Stable, reliable performance

Areas to Watch:

• PR review backlog (especially Fix clean problem and tidy up #172 - nearly 2 years old)
• Older open issues accumulating
• Feature requests waiting for evaluation
• Community contributor patience being tested

---

🎉 Closing Thoughts

The rebar3_gpb_plugin project demonstrates excellent stewardship with rapid dependency updates, consistent releases, and strong documentation. The repository is healthy and well-maintained!

A focused 1-2 hour session this week to review PR #172 would be a tremendous win for the project and the community. This simple action would:

• Fix a real user-reported bug
• Show appreciation for community contributions
• Close a nearly 2-year-old PR
• Simultaneously close issue plugin clean proto output files failed. #176
• Boost repository health metrics

Combined with some strategic issue triage, this would elevate the repository's health to an even higher level.

Great work maintaining this essential Erlang protobuf tooling! 🎊 The Erlang community benefits greatly from this reliable infrastructure.

---

This report was automatically generated by the Weekly Repo Status workflow
Reporting period: March 10-16, 2026

Generated by Weekly Repo Status

To install this workflow, run gh aw add githubnext/agentics/workflows/daily-repo-status.md@eb7950f37d350af6fa09d19827c4883e72947221. View source at https://github.com/githubnext/agentics/tree/eb7950f37d350af6fa09d19827c4883e72947221/workflows/daily-repo-status.md.