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

Bump go-gitub to v60 #2188

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

nayuta
Copy link

@nayuta nayuta commented Mar 9, 2024

Resolves #2187


Before the change?

  • go-github v57.0.0

After the change?

Pull request checklist

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • No

@nayuta nayuta marked this pull request as ready for review March 11, 2024 04:38
@kfcampbell
Copy link
Member

I've resolved the merge conflict, though I'm a little hesitant about the HookConfig changes. The strongly-typed HookConfig struct means we can no longer change 1 to true in the insecureSslStringToBool function. We could remove that line entirely, though that means #2196 would essentially be undone. @EttoreFoti do you have thoughts on this change?

Our docs are pretty vague about this: insecure_ssl says "string or number" next to it. Presumably the string is meant to represent a boolean there, though the docs text mentions only 0 or 1 as valid options.

@EttoreFoti
Copy link
Contributor

I've resolved the merge conflict, though I'm a little hesitant about the HookConfig changes. The strongly-typed HookConfig struct means we can no longer change 1 to true in the insecureSslStringToBool function. We could remove that line entirely, though that means #2196 would essentially be undone. @EttoreFoti do you have thoughts on this change?

Our docs are pretty vague about this: insecure_ssl says "string or number" next to it. Presumably the string is meant to represent a boolean there, though the docs text mentions only 0 or 1 as valid options.

@kfcampbell this is bumping 3 major version of the GitHub client which is core in the provider, all test should be rerun before approving, I'm testing on the issue that was fixed but is unfixed by this PR, I'll create new PR with fixed once done.

@connor-miller-kr
Copy link

Any update on this PR?

@Simon-Boyer
Copy link

Simon-Boyer commented May 17, 2024

@kfcampbell what is missing for this PR to go forward? Is there anything I can do to help?
I have a project that would need to define rulesets with custom properties and we need go-github v60 to implement this properly in the provider.
@nayuta If you dont have time to work on this right now, could you give me permission to write to your fork so I can give a hand?

@EttoreFoti
Copy link
Contributor

@kfcampbell what is missing for this PR to go forward? Is there anything I can do to help? I have a project that would need to define rulesets with custom properties and we need go-github v60 to implement this properly in the provider. @nayuta If you dont have time to work on this right now, could you give me permission to write to your fork so I can give a hand?

@Simon-Boyer this is breaking a bunch of resources, being an update of the main SDK the full test suite needs to be run to ensure nothing breaks

@nayuta
Copy link
Author

nayuta commented May 20, 2024

@nayuta If you dont have time to work on this right now, could you give me permission to write to your fork so I can give a hand?

@Simon-Boyer I quickly fixed compile errors and invite you to the repo.

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.

[MAINT]: Bump go-github to v60
5 participants