-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need help knocking down issues #169
Comments
@markjbrown, I'd be more than happy to help in any way I can. |
@markjbrown I updated the .NET 8 branch I created a while back and started #172 from it. I haven't run any integration tests yet but will do that when I can. |
@markjbrown @philnach and I both checked #172 but it needs another approval so it can get merged. @crpietschmann |
ok, got it. Looks good. Approved and hit the merge button on it. I'm going to take a look and close some issues here that would be covered via this PR. |
@stefanedwards thanks. Been meaning to close some of these. I ran the GH actions on #152 looks good. I need to get @bowencode to review before merging as it touches parts of this code base he is most familiar with. Thanks! |
Hi folks. The issues list for this project is getting really long. Is there anybody that would be willing to take on any of these? There are some critical items that need immediate attention.
@bowencode, @crpietschmann, @hsavran, @codingbandit if any of you have cycles and can help, let me know. I'd like to setup some time to triage and prioritize. There is a backlog of PR's that are blocked because of #167. Also the .NET Fx for this thing badly needs to be updated. This would close a number of other Issues I see as well.
Let me know if anyone can help. I'll set up a bridge to discuss.
thanks.
The text was updated successfully, but these errors were encountered: