This should also be gated if they open a pull request (the bot should not auto-assign if they are gated.) Be sure that the order of precedence is repo, org, then global. Example scenario:
contributor has 0 repoXP, 50 orgXP, 100 globalXP.
config expresses that the task they want to start has:
min-xp of { repo: 100, org: 0, global: 0 } -> rejected (their repoXP is 0)
min-xp of { repo: 0, org: 50, global: 0 } -> OK (their orgXP is 50)
min-xp of { repo: 0, org: 25, global: 1000 } -> OK (their orgXP is 50)
This should also be gated if they open a pull request (the bot should not auto-assign if they are gated.) Be sure that the order of precedence is
repo,org, thenglobal. Example scenario:0 repoXP,50 orgXP,100 globalXP.min-xpof{ repo: 100, org: 0, global: 0 }-> rejected (their repoXP is 0)min-xpof{ repo: 0, org: 50, global: 0 }-> OK (their orgXP is 50)min-xpof{ repo: 0, org: 25, global: 1000 }-> OK (their orgXP is 50)