@Keyrxng, this task has been idle for a while. Please provide an update.

@rndquu I can't re-open, would you mind doing it for my PRs in this repo. Sorry for the inactivity, been dealing with a bereavement.

This can be reviewed--I've merged in #30 so maybe after it's merged?

Right now when you select Full Default you are prompted to enter the required fields (evm private key) which is clean UI. Once the push is made, the configs are expanded and all values are visible. Is this the preferred outcome? Or should it look like this?

1. Expanded on install let's partners see what is configurable and what everything is currently set to without deep diving all plugins.
2. Minimized on install requires they go investigating plugins or the Custom section of the particular plugin they have in mind.

[!CAUTION]
[universal-github-app-jwt] Private Key is in PKCS#1 format, but only PKCS#8 is supported. See https://github.com/gr2m/universal-github-app-jwt#private-key-formats

This might be related to pull precheck based on converting the pull from draft to ready.

It also makes sense that we just now started seeing this error because it's a brand new feature.

@gentlementlegen @whilefoo rfc

This might be related to pull precheck based on converting the pull from draft to ready.

It also makes sense that we just now started seeing this error because it's a brand new feature.

@gentlementlegen @whilefoo rfc

It comes from command-start-stop and it was triggered when the PR body was edited so it seems to be the same issue as here

@Keyrxng Sorry for the noise, this task was chosen for testing the issue with command-start-stop.

No worries ty for the heads up