rupertdenton

Interesting - what do you mean? Like the solution to a bug?

Thanks for the reply. What do you think turns people off documentation? I hear about doc rot etc. Sounds like you've really seen the light. One of the issues I've had with docs is that they are quite non-visual, I tend to diagram quite a lot to get a sense of how things hang together.

Yeah nice! I have a gridded moleskine for the same purpose. Trouble is I tend to just write notes as I go and then not really refer back to them. Effectively an ephemeral scratch pad.

That's really interesting. So just so I understand the wrapper command automated those steps you've outlined? What were the convenience commands?

This is a really interesting set of insights. I definitely see the theoretical benefits of stacking but as you indicate it feels like it requires a pretty good grip of git to manage. Do you have tooling to support with this in your team? To your last point, so let's say you've got 5 stacked PRs chained off of each other, you then need to merge master into each of them individually?

Yeah merge hell is what sorta keeps me shy of doing the stacked approach. Is this something you've encountered?

Nice that sounds like a really neat workflow. I haven't used stacked PRs before, I feel like everywhere I've worked has generally been: work on a feature, PR/MR the branch and try to keep it small. Any idea what it isn't more common?

Yeah I did a bit of a deep dive on Pullpo - it looks great, small passionate team! I was curious if there is anything that you don't like about using it as part of your workflow? Like I can see your colleagues prefer a specifically different type of workflow - why did your team adopt it?

Wow, how have you found that improves things for your team?

Oh interesting, hadn't heard about this. Do you like it? Any parts that aren't great? I'm definitely open to new tools!

That's awesome! Can I ask what sort of feedback you were getting that lead to CodeApprove. I agree that sitting with the incumbents shouldn't be our default setting, curious about which parts you are trying to improve?

Yep! It does this. You'll be prompted with a popup to confirm if you want to switch branches. If you don't confirm it won't do anything.

Hey, thanks so much for the kudos. This is a solid point. I'm going to talk with the team about prioritising an export function.

Each CodeNote is essentially a node of links to that code (and conversations about that code) in other places: VCS Hosts, editors, Slack etc. The generated VCS Host and Slack permalinks are not dependant on us. So we can, at least, create a dump of those in short order.

We use websockets to locate the code in editors, but could easily downgrade these to protocol links (e.g. `vscode:`) that are independent of us also.

What format would be most useful for the dump to be in? JSON, CSV, markdown ...? I'm thinking JSON just from a data organisation perspective?

Hey there, really important question.

There's no security risk here. If you don't have the creds to access the repo, there is no way you can check out the code.

You can try this CodeLink to see how it works: codelink.dev/CKy5YDEZg. The link is to our open demo repo on GitHub. Click open in VS Code or JetBrains and you'll see the prompt in your editor to select a folder to check the code into, it'll then open the file and highlight the lines.

Hey! Just following up. We tried to recreate your issue but had no luck. We’d love to follow up with you and get this figured out. You can join our community discord and give us a bell: https://discord.gg/EXEuv2Ym

Hey thanks for letting us know. We are looking into this!

Hey! Thanks for the comment. CodeLink also auto loads lines of code seamlessly in VS Code, JetBrains, GitHub, GitLab, BitBucket etc. It also makes it easy if you don't have the repo locally - it'll check it out for you. If you're not on the right commit/branch it'll swap to it for you. It'll also unfurl the code on Slack (more integrations inbound!) and allow people you share it with to open it up in their IDE or VCS! Hopefully makes life easier for our fellow devs :)

Thanks so much for the comment. Yes further integrations are definitely on our very near future roadmap, oembed too!

Yes! We are really pleased to support JB.

That's great! I've shared this feedback with our team and we are really glad you are happy with it. Please do share any more feedback with us if you have any!!

Hey! Thanks again for this - I wanted to pass on some additional comments from our Founder too. He was really interested in your response but was having trouble posting.

Nice! So you've seen what a CodeLink is. Imagine if that link was a snippet of code embedded in a web doc, like Google Docs or Confluence.

You could then write a tutorial with snippet blocks that - when clicked - load up the repo and highlight that code in your editor.

Plot twist, we've built it: CodeNote (www.codenote.dev) - think Notion but for Developers. It works hand in hand with CodeLink.

We use it to onboard all new devs and for technical design specs etc. We've got a closed Beta group actively using it. If you like, jump on the wait list on the website and we'll get you in the next group.

Looking forward to seeing you in there and getting your feedback!

That's great to hear - we are really pleased to offer integrations with multiple IDEs to support as many devs as possible. If you get a chance to test it out on your JB set up, would love to hear your thoughts.

Hahaha. Onion on belt energy: https://www.youtube.com/watch?v=a6Dc7W6jXCo

That's really interesting. How do you find using that process? I haven't seen it in action.

That is awesome feedback. We actually have some features on our roadmap that really align with this. Its great to have it validated here, so thank you for taking the time to respond. We are a small team, but really passionate about making something really helpful!

That is awesome to hear, thanks so much. We've also got slack integration so your codelinks unfurl really nicely in Slack (if you use it with your teams/friends/community). We're really keen for feedback so please do share the good and the "needs work" (especially the "needs work" haha)

Hey, thanks for the comment. Another commenter also shared this plugin, looks interesting! We are trying to really help devs get on the same page fast when sharing code with one another - so the codelinks you can share via CodeLink unfurl in slack (we've got more integrations coming too) and link directly to the code in your repo or IDE. We also integrate with JetBrains which was some feedback we got from our early users - definitely keen for feedback so appreciate yours, keep it coming!