WIP: Add new fields to GH repos + handle null bools #3926
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
please undraft this once you think it is ready |
tas50
force-pushed
the
tas50/new_gh_repo_fields
branch
from
351f265 to
521ab86
Compare
tas50
force-pushed
the
tas50/new_gh_repo_fields
branch
from
521ab86 to
06e5e81
Compare
Add new fields + handle a few merge options that are bools with null values if not set Signed-off-by: Tim Smith <[email protected]>
tas50
force-pushed
the
tas50/new_gh_repo_fields
branch
from
06e5e81 to
29b461d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add new fields + handle a few merge options that are bools with null values if not set
WIP as I'm digging into some odd behavior with some existing bools