Live data from Hacker News

Google Workspace CLI

github.com

261–270 of 316 posts

Re: Google Workspace CLI

#261

Earlier quoted context omitted.

I mean, they are? GCP usage/revenue is growing faster than AWS and Azure. Mostly driven by Gemini pushing folks onto the platform and them deciding "why not move everything else too".

Wait, I am curious how Gemini "pushes" devs to GCP.

Colocating data and discounts. Cross cloud transfers are painful, and Google has a ton of on-cloud easy button integrations with Gemini and their data products.

Re: Google Workspace CLI

#262

Earlier quoted context omitted.

Paste from markdown (Chrome only) works _really_ well for me. What are the extra steps you’re running into?

Interesting, in my Arc browser, I just tried File -> open -> upload -> blah.md and it does seem to render fine. This exact thing did not work a few weeks ago, meaning the various header markers etc showed up as raw "##" etc, and I had to further select something like "open as new doc" to finally make it look good.

Right click > "Paste from Markdown" instead of just straight up pasting in

Re: Google Workspace CLI

#263
post #220

Earlier quoted context omitted.

We have been using something similar for editing Confluence pages. Download XML, edit, upload. It is very effective, much better than direct edit commands. It’s a great pattern.

I would be very interested in this if you could share? Maintaining a Knowledge Base without a Git workflow is a pain currently.

You can use the Copilot CLI with the atlassian mcp to super easily edit/create confluence pages. After having the agent complete a meaningful amount of work, I have it go create a confluence page documenting what has been done. Super useful.

Re: Google Workspace CLI

#264

[flagged]

Generally, this disclaimer is required for products that are released under the "Google" name but without any kind of support guarantees for enterprise customers. That or it's a personal project that IARC decided could live in the workspace project. Disc: Former Googler

> but without any kind of support guarantees for enterprise customers

Also known as every single Google product

Re: Google Workspace CLI

#266
post #262

Earlier quoted context omitted.

Interesting, in my Arc browser, I just tried File -> open -> upload -> blah.md and it does seem to render fine. This exact thing did not work a few weeks ago, meaning the various header markers etc showed up as raw "##" etc, and I had to further select something like "open as new doc" to finally make it look good.

Right click > "Paste from Markdown" instead of just straight up pasting in

Images wouldn't work though, right? I'd be amazed if that worked. My CLI tools handle those.

Re: Google Workspace CLI

#267
post #220

Earlier quoted context omitted.

I would be very interested in this if you could share? Maintaining a Knowledge Base without a Git workflow is a pain currently.

I'm afraid I can't easily share this, as we have embedded a lot of company-specific information in our setup, particularly for cross-linking between confluence/jira/zendesk and other systems. I can try explain it though, and then Claude Code is great at implementing these simple CLI tools and writing the skills. We wrote CLIs for Confluence, Jira, and Zendesk, with skills to match. We use a simple OAuth flow for user…

Thanks for the insights!

We have been doing something similar but it sounds like you have come further along this way of working. We (with help from Claude) have built a similar tool that you describe to interface with our task- and project management system, and use it together with the Gitlab and Github CLI tools to allow agents to read tickets, formulate a plan and create solutions and create MR/PR to the relevant repos. For most of our knowledge base we use Markdown but some of it is tied up in Confluence, that's why I have an interest in that part. And, some is even in workflows are in Google Docs which makes the OP tool interesting as well -- currently our tool output Markdown and we just "paste from markdown" into Gdocs. We might be able to revise and improve that too.

Re: Google Workspace CLI

#268

Related, I often work with markdown docs (usually created via CLI agents like Claude Code) and need to collaborate with others in google docs, which is extremely markdown-unfriendly[1], so I built small quality-of-life CLI tools to convert Gdocs -> md and vice versa, called gdoc2md and md2gdoc: https://pchalasani.github.io/claude-code-tools/integrations/... They handle embedded images in both directions. There are si…

interesting we have a very similar internal flow - we like working in markdown but our customers want to leave feedback in Google docs, so we also have an md -> gdoc tool. We don't do the reverse as we ask them to only leave comments/suggested changes and we apply those directly to the markdown and re-export.

I ran into similar issues as you for the image handling, and the work around I use is to use pandoc to convert to docx as a first step and then import that as a Google Doc using the API, as Google Docs seems to handle docx much better than markdown from what I've seen.

Re: Google Workspace CLI

#269
post #159

Earlier quoted context omitted.

Not because it's fast, but because of its compiler. It acts as a very good guardrail and feedback mechanism for LLMs.

Typescript has surpassed Python and JS as most used on Github for a similar reason https://xcancel.com/github/status/2029277638934839605?s=20

> making strict typing an advantage, not a chore

It's crazy that people think strict typing is a chore. Says a lot about our society.

Re: Google Workspace CLI

#270
post #262

Earlier quoted context omitted.

Right click > "Paste from Markdown" instead of just straight up pasting in

Images wouldn't work though, right? I'd be amazed if that worked. My CLI tools handle those.

Obsidian has become almost an operating system for working with markdown. Its Live View / Edit mode is excellent (WYSIWYG) and its ability to accept pasted content and handle it appropriately is good and getting better. Its plugin/extension ecosystem is robust (and has a low barrier to entry), and now that it has a CLI I expect to see an acceleration of clever workflows and integrations.

No affiliation, just a very happy ~early adopter and daily user.

Post reply on HN