-
Notifications
You must be signed in to change notification settings - Fork 11
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
IFC-761 Use flags to handle branch permissions #4601
Conversation
CodSpeed Performance ReportMerging #4601 will improve performances by 16.35%Comparing Summary
Benchmarks breakdown
|
d6f2bd4
to
b7030e2
Compare
27fa034
to
c6f6c7b
Compare
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.
LGTM. Goes the ALLOW_ALL and ALLOW_OTHER work interchangeably within a non default branch now? I.e. if a user has either of those permissions an action would be allowed?
# What do we do if edit default branch global permission is set? | ||
# if not restrict_changes: | ||
# for key in permission_report: | ||
# permission_report[key] |= PermissionDecisionFlag.ALLOW_DEFAULT |
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.
Can it be an argument to get_permission_report()
?
For some reasons the issues on appear when we run tests in a row: * backend/tests/unit/graphql/test_mutation_create.py::test_create_object_with_node_property * backend/tests/unit/graphql/test_mutation_create.py::test_create_object_with_single_relationship_node_property * backend/tests/unit/graphql/test_mutation_create.py::test_create_object_with_multiple_relationships_with_node_property We should find a better fix for this.
d94284a
to
5b9fd80
Compare
No description provided.