Everybody mike nichols designer for web IDE and snippets. I'm gonna go over some of the items we are working on for 13.1. So over the last couple of milestones, we've been converting snippets to be get based, and a lot of that work has already been completed and will continue in 13.1, but now the snippets are get based. It opens up some opportunities and new things that we can do with them. So a couple of items related to that. So this first one here, project based snippets, should follow project access permissions.

So this is the idea that right now, snippets are only permission to the person that originally created them and when they're created in the context of a project that may or may not make sense. So this proposal is to change those permissions to be more in line with the rest of the project level. Permissions. As you can see, it is a pretty popular proposal.

We're really just doing our due diligence there to make sure what we are proposing is the correct path and also figuring out kind of the messaging in the rollout plan of how we shift this permissions and the impacts that that might have some other snippets related items based on git is implement revisions tabs. So now that there give based you can make revisions to them similar to like a commit history. So this will be investigating adding a tab.

That kind of shows the history of snippets and the changes that have been made again very similar to a commit based thing, and another item is add new from so being good base. We it's opened up the opportunity that we might be able to import from various sources that are get based, snippets, which will help kind of move some snippets from other places, possibly into get lab on the other side of things on the web. Ide side really kind of just doing some cleanup items in this there's a few in here.

Like the min map, the colors were a little bit difficult disease, we're enhancing the colors no longer gonna hide the commit tab when there aren't any changes, and then this one was an interesting one, because it touches kind of the flow of things that happens when you fork a project.

So this is what happens when you are presented with the ID IDE button in a project that you've already made a fort for so right now it opens the current project, which you can't edit, and the proposal here is to open up the fork, which gives a more direct path to the happy path of allowing you to edit in your fork and then commit via merge requests back to the original repository and then the last one here on the list is, is for the last 200 is moving the the notification of the number of changes again into the sidebar and just cleaning up some error messaging for the code owner or failure, error message that can occur.

So that's it. I will link this board in the issue or in the video description and.