NodeGit + SQLite #3585
Merged
NodeGit + SQLite #3585
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Install NodeGit package * Fix nodegit package installation (#3512) * Change node_version to 10.16.0 * Define node & electron engines in package.json * FIX: Add comma after node version engine * Switch back to latest version of Node@10 * Split script command yarn and yarn build:window * Update "postinstall" script command to install electron app deps * Install electron app native deps * Merge yarn && yarn postinstall && yarn build:linux command * Test windows pipeline with npm * Upgrade nodegit & electron-builder package * Run pipeline in npm * Run audit fix * Run install && audit fix * install & audit fix & postinstall & build:window * Update build description * Move yarn to npm * Update echo command * Remove electron from engines * Update npm registry url * Initialize repo using nodegit * Use promise instead of async * git status (nodegit)
mittalyashu
added
Git
|
Hey there! We would appreciate if you could provide us more information about what you're trying to accomplish here! |
Remove function for getting remote url on adding repository and only validate git repository.
Source column tells the source of repository (local or remote repo)
Getting repository git status along with each file type, symbol, and color.
Remove fileChangesSkeleton and use status-list component
* Use nodegit * Use database * Add cloning progress * Run ESLint
* Use nodegit and database instead of simple-git for initialize repository feature * Disable git features for non-initialized repositories * Add initialize repository feature from homepage This commit includes an anti-pattern because of mutating this.isGit prop inside component but this can't be avoided without making some major changes.
* Get & set settings to localStorage Using if/else statement in beforeCreate lifecycle hook insted of using in vuex store mutation * Add AutoInit settings to experimental page * typo: initialize spellings * Dispatch update to settings store (in single line) * fix: autoInit undefined value in settings store #3596 (comment)
* auto initialize non-git repository * Update repositoryItem.vue after `npm run lint:fix` * Do not initialize new repository on create * Fix blocking error on new repository creation when folder does not exist Co-authored-by: Yashu Mittal <mittalyashu77@gmail.com>
Incase error event a message can be shown inside the modal. Reference: #3599 (comment)
Creating a updateIsGitStatus mutation to update isGit value inside repository vuex store. Database is updated with the required changes with vuex is unaware of the changes which causes is bug to show repository as `isGit: false`. Reference: #3599 (comment)
replace package-lock.json with yarn.lock
mittalyashu
force-pushed
the
chore/add-nodegit
branch
from
7166382
to
4c92c94
Compare
|
Merging this PR without successful build. |
|
Unsure (don't remember) of the changes this PR contains with respect to #170 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE: This PR added a major upgrade in Node v14
To know more about this PR, read this issue #170
TODO:
Revert backazure-pipelinechanges