Initialize repository (nodegit)

[KaKi87]

The purpose of this PR is to replace the old simple-git/localStorage code by the new nodegit/sqlite methods to perforn a repository initialization using NodeGIt's API and the addRepository mixin.

[mittalyashu]

😅

[mittalyashu]

Initializing repository feature includes many sub-features:

1. Block user to open workspace page if repository is not initialized
2. User should still be able to access settings page
3. Update repository data in database
4. Show repository git init status on welcome page
5. Create a app settings for auto-initialise git repository or manual process

FAQ

Which case can you have a local and saved non-initialized repository?

Allowing users to add non-git repository and later adding option to initialize git repository directly from thermal app is an handy feature.

It is for those situations where the user just wants to add a project to Thermal but doesn't want to initialise the repository.

Also it will give user more control over how they want to initialize the repository.

[KaKi87]

• Block user to open workspace page if repository is not initialized
• User should still be able to access settings page
• Update repository data in database
• Show repository git init status on welcome page
• Create an app setting for auto-initialize git repository or manual process

[mittalyashu]

Block user to open workspace page if repository is not initialized

How about hiding the sidebar if the directory is not a git repository?

[KaKi87]

That's what I wanted to do next. Unfortunately, I didn't found out how to do that considering the current UI structure.

[mittalyashu]

Yeah, I am also not sure hiding the sidebar for non-git repository is the right choice.

[mittalyashu]

Create an app setting for auto-initialize git repository or manual process

This PR will cover this feature #3596

[KaKi87]

What do you think is the right choice ?

[mittalyashu]

About what?

[KaKi87]

Yeah, I am also not sure hiding the sidebar for non-git repository is the right choice.

[mittalyashu]

Even if we try to disable each item individually in the sidebar that will be a lot of work.

So, to make the process easier, the only possible option is left to hide the sidebar.

[KaKi87]

Even if we try to disable each item individually in the sidebar that will be a lot of work.

I'd like to point out that this is proof that there's a design issue in the DOM structure, it should be simpler.

[mittalyashu]

I'd like to point out that this is proof that there's a design issue in the DOM structure, it should be simpler.

What do you mean? Can you elaborate it with some examples?

Right now, we have

<router-link
	class="repository__sidebar__item"
	:to="{ name: 'repositoryHistory' }"
>
	<t-flexbox align-items="center">
		<clockIcon />
		<p>History</p>
	</t-flexbox>
</router-link>

<router-link> based linked wrapped in a parent div tag. This is a very simple HTML structure we are following like list of items.

After the basic NodeGit integration is done, I was thinking to work on sidebar and change the HTML structure to something like this: