You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Quarkus repo is (rightly) a bit strict about what we allow to merge, and in particular requires approval before merging.
That's annoying when someone just wants to change something to their participant config, such as the max number of issues for a given category.
We should consider moving part of the configuration to the "reports" repository. Either:
put the all config in quarkusio/quarkus-github-lottery
put the main config in quarkusio/quarkus and per-participant config in quarkusio/quarkus-github-lottery
put the main config in quarkusio/quarkus and per-participant config in the main description of per-participant issues quarkusio/quarkus-github-lottery
We could also add a command such as /lottery subscribe to have configuration initialized. That would be necessary for item number 3 in particular, since initializing a per-participant issue is not trivial.
The text was updated successfully, but these errors were encountered:
The Quarkus repo is (rightly) a bit strict about what we allow to merge, and in particular requires approval before merging.
That's annoying when someone just wants to change something to their participant config, such as the max number of issues for a given category.
We should consider moving part of the configuration to the "reports" repository. Either:
We could also add a command such as
/lottery subscribe
to have configuration initialized. That would be necessary for item number 3 in particular, since initializing a per-participant issue is not trivial.The text was updated successfully, but these errors were encountered: