deps

Optional dependencies should not be treated as a "dependency" kind, of which there are only three -- regular, build, and dev. "Optional deps" should instead be handled as a boolean flag, which is what cargo does. A dependency can be both a build dependency and optional simultaneously, but currently cargo-deps will erase one of these.

Optional dependencies can be displayed with a dashed line.

See below:

~/tmp/foo ➜ corral add github.com/seantallen/lori.git --revision 0.0.1
~/tmp/foo ➜ cat corral.json
{
  "packages": [],
  "deps": [
    {
      "locator": "github.com/seantallen/lori.git",
      "version": ""
    }
  ],
  "info": {
    "description": "",
    "homepage": "",
    "license": "",
    "documentation_url": "",
    "version": "",
    "name": ""
  }
}

A new setting can be added called github_automerge. This would enable (or disable) the auto-merge option on a PR after it is created (or updated). At this point, it would need to use the GraphQL API because auto-merge isn't a part of the REST API yet:
https://docs.github.com/en/graphql/reference/mutations#enablepullrequestautomerge

The end of this function would be the place to start:
https