inbuxa-admin only shows the Settings pages the served schema lists, so the upcoming Relays page needs a link there: CustomComponent/Relays, under MTA › Outbound, right after Routes. Only the layout changes; expr-schema --check and the fork checks are clean.
The console page itself comes in an inbuxa-admin PR. Until that lands, consoles hide this link, because they don't show a CustomComponent page they can't draw.
inbuxa-admin only shows the Settings pages the served schema lists, so the upcoming Relays page needs a link there: `CustomComponent/Relays`, under MTA › Outbound, right after Routes. Only the layout changes; `expr-schema --check` and the fork checks are clean.
The console page itself comes in an inbuxa-admin PR. Until that lands, consoles hide this link, because they don't show a `CustomComponent` page they can't draw.
inbuxa-admin shows only the Settings pages the server's schema lists, so
its Relays page needs a link there: CustomComponent/Relays, under MTA ›
Outbound, after Routes. Nothing else in the schema changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
inbuxa-admin only shows the Settings pages the served schema lists, so the upcoming Relays page needs a link there:
CustomComponent/Relays, under MTA › Outbound, right after Routes. Only the layout changes;expr-schema --checkand the fork checks are clean.The console page itself comes in an inbuxa-admin PR. Until that lands, consoles hide this link, because they don't show a
CustomComponentpage they can't draw.