Same - projects that span repos + GitHub wiki are great for the PM side, and being inside github is great for the developer side.
An important part is that Graphistry's devops is largely run via GitHub actions triggered by PR labels as well (ex: pr label -> you have a new copy of production running), so lifecycle visibility comes as part of working vs extra documentation effort.
An important part is that Graphistry's devops is largely run via GitHub actions triggered by PR labels as well (ex: pr label -> you have a new copy of production running), so lifecycle visibility comes as part of working vs extra documentation effort.