When parent/child team requests are made from someone who is not an organization owner or a maintainer of both teams, the requests move to a pending state. While in that pending state, the entitlements user cannot provision the parent/child teams correctly until an owner approves or denies that non-owner request.
This could lead to an unusual outcome of entitlements-app showing all of the correct signs of the parent and child teams being correct, but the actual GitHub.com state being incorrect due to the pending request.
If we're going to set or change the parent team and it's pending, could the entitlements user approve/deny the request in order to correctly set it? If not, can we at least be obvious that there's a pending state in the logs?
When parent/child team requests are made from someone who is not an organization owner or a maintainer of both teams, the requests move to a pending state. While in that pending state, the entitlements user cannot provision the parent/child teams correctly until an owner approves or denies that non-owner request.
This could lead to an unusual outcome of
entitlements-appshowing all of the correct signs of the parent and child teams being correct, but the actual GitHub.com state being incorrect due to the pending request.If we're going to set or change the parent team and it's pending, could the entitlements user approve/deny the request in order to correctly set it? If not, can we at least be obvious that there's a pending state in the logs?