-
Notifications
You must be signed in to change notification settings - Fork 24
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
Update away from deprecated GitLab field #3924
base: main
Are you sure you want to change the base?
Conversation
@@ -39,7 +39,7 @@ func initGitlabGroup(runtime *plugin.Runtime, args map[string]*llx.RawData) (map | |||
args["requireTwoFactorAuthentication"] = llx.BoolData(grp.RequireTwoFactorAuth) | |||
args["preventForkingOutsideGroup"] = llx.BoolData(grp.PreventForkingOutsideGroup) | |||
args["mentionsDisabled"] = llx.BoolData(grp.MentionsDisabled) | |||
args["emailsDisabled"] = llx.BoolData(grp.EmailsDisabled) | |||
args["emailsDisabled"] = llx.BoolData(!grp.EmailsEnabled) |
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.
we should also add the new field and mark the old one as deprecated
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.
I'd prefer to just update the call under the hood and keep our fields the same. I don't think we need to match our fields to their underlying API 1:1 in every case. The fields are named pretty consistently which is nice and it wouldn't benefit the user to switch them unless they remove all the "disabled" calls in the future.
Keep our field the same, but avoid this deprecated call Signed-off-by: Tim Smith <[email protected]>
03302db
to
a4a6023
Compare
Keep our field the same, but avoid this deprecated call