-
Notifications
You must be signed in to change notification settings - Fork 3
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
Modernize tools #6
Conversation
81b3e08
to
51e0733
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In PrepareRelease, since we can't have extension methods in a file with top-level statements, I put them in a separate class.
But then it was ugly to have them access the repo name as a static field, so I refactored the class into a wrapper around GitHubClient.
If you preferred it as it was before, we don't have to use top-level statements, I can just revert the changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @thomaslevesque. I'm happy with everything. A little confused about one comment, but if you're good, I'll merge.
Thanks, @thomaslevesque! |
Use top-level statements in programs
Use implicit usings
Refactor GitHubClient extension methods into GitHubClient wrapper class
Remove a redundant PackageReference Remove element