-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
fix: Allow removing/unsetting repository custom property #3309
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3309 +/- ##
==========================================
- Coverage 97.72% 93.05% -4.67%
==========================================
Files 153 172 +19
Lines 13390 11772 -1618
==========================================
- Hits 13085 10955 -2130
- Misses 215 723 +508
- Partials 90 94 +4 ☔ View full report in Codecov by Sentry. |
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.
Thank you, @felixlut !
LGTM.
Awaiting second LGTM+Approval from any other contributor to this repo before merging.
Thank you, @tomfeigin ! |
Could we get a new release with this change as well? I have some changes over the last couple of weeks that will unblock some stuff I'm working on in https://github.com/integrations/terraform-provider-github: |
Yes, I can work on a new release later today. |
This has now been released here: |
This change will allow a user to set
null
when calling the create/update repository custom property endpoint. As written in the docs, doing so will remove/unset the custom property. Currently doing so is not possibleNormally I think this would count as a breaking change, since this will modify the behavior when omitting the
Value
, but I believe this is a straight up bug, as omitting theValue
should always result in an error. So there shouldn't be any usages that's relying on this behavior. Technically it's possible, but improbable.