Skip to content
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

Add fields to update repository API and create branch protection API to match GitHub APIs #2709

Merged
merged 1 commit into from Mar 17, 2023

Conversation

verbanicm
Copy link
Contributor

No description provided.

@gmlewis gmlewis changed the title add fields to update repository api and create branch protection api to match github apis Add fields to update repository API and create branch protection API to match GitHub APIs Mar 17, 2023
Copy link
Collaborator

@gmlewis gmlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @verbanicm and @sethvargo !
LGTM.
Merging.

@codecov
Copy link

codecov bot commented Mar 17, 2023

Codecov Report

Merging #2709 (2b4ee89) into master (9bfbc00) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2709   +/-   ##
=======================================
  Coverage   98.05%   98.05%           
=======================================
  Files         131      131           
  Lines       11459    11459           
=======================================
  Hits        11236    11236           
  Misses        152      152           
  Partials       71       71           
Impacted Files Coverage Δ
github/repos.go 98.84% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@gmlewis gmlewis merged commit 9e4a1fd into google:master Mar 17, 2023
9 checks passed
@verbanicm
Copy link
Contributor Author

Thank you @gmlewis !

@verbanicm verbanicm deleted the verbanicm/update branch March 17, 2023 16:32
@verbanicm
Copy link
Contributor Author

@gmlewis Do you have a set release schedule or can this be cut whenever?

@gmlewis
Copy link
Collaborator

gmlewis commented Mar 17, 2023

@verbanicm - we typically shoot for a release approximately once per month, but we are flexible and can release on demand if there is a pressing need. We are already at 3 weeks since the last release so I can go ahead and prepare a new one.

@verbanicm
Copy link
Contributor Author

@gmlewis No rush, but you are able, then 🎉

@gmlewis
Copy link
Collaborator

gmlewis commented Mar 17, 2023

@verbanicm - here is the latest release: https://github.com/google/go-github/releases/tag/v50.2.0

@verbanicm
Copy link
Contributor Author

@gmlewis Awesome, thank you!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants