Matt Pollard

~Yep! The text you've highlighted is still sensible.~ Oof, I just noticed that the bold text atop that notice should not be "GitHub Enterprise Server". Lemme fix that...

@sergiou87, I pushed https://github.com/desktop/desktop/pull/16953/commits/7ab5195014a25a01e6980cbe95c83e9016b772fd to address this. However, it's a long string 😅 Could you see how it renders? We _could_ go with just "GitHub Enterprise", but I think titling...

That's a good call. I'll look back through the changes in the next week or so and determine which really refer to GHES _instances_, versus GitHub Enterprise _the plan_ 👀

We need to think a little more about this change. We're tracking that internally. I'll close this PR 🙏🏻 Thanks for your help, everyone!

@timja 👋🏻 Sorry, I lost track of this. The doc you links to looks alright to me, and doesn't seem to mention copying a key. Can you clarify?

We need to flesh this out a bit. I've asked internally to see if we have any examples of this procedure that we can use to write the docs 👀

Here's a short plan for these changes: 1. In "[Increasing CPU or memory resources](https://docs.github.com/[email protected]/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources)", create a new section called "Adding CPU or memory resources for Google Cloud Platform". 2. Within...

@cmwilson21 👋🏻 This should be ready for someone to pick up!

Hi, @CBID2 👋🏻 Thanks for the heads up, and the contribution 🤩 Per the body of your PR and your comment about the introduction, I've provided a little initial feedback...

Gotcha 🙇🏻 No worries... thanks for giving it a shot, and for letting us know!