~$ sudo npm install -g @deliverymanager/gitsync
~$ gitsync --pull
~$ gitsync --clone
~$ gitsync --all
~$ gitsync -a
~$ gitsync --init
~$ gitsync --checkout
Repository description: path/to/folder
-> Will clone the repository in ./path/to/folder/<repository name>
Repository description: Some description
-> Will show a warning and not clone
The following file, .gitsync.json, must be placed in the home folder and is required for authentication with the GitHub API:
{
"user": <github username>,
"user_agent": <github user_agent>,
"sync_account": <account from which to sync>,
"org": <true/false> // whether the sync_account is an organization
}
{
"user": <github username>,
"user_agent": <github user_agent>,
"sync_account": <account from which to sync>,
"org": <true/false> // whether the sync_account is an organization,
"at": <github API access token>
}
{
"user": <github username>,
"at": <github API access token>,
"test_repo_1": {
"name": <repo name>,
"full_name": <repo full name>,
"local_path": <local path to which the repo will be cloned>
},
"test_repo_2": {
"name": <repo name>,
"full_name": <repo full name>,
"local_path": <local path to which the repo will be cloned>
},
"user_agent": <github user_agent>,
"sync_account": <account from which to sync>,
"org": <true/false> // whether the sync_account is an organization
}
You can place the file yourself or you could run ~$ gitsync --init
which will prompt for user name and Github API access token.
~$ gitsync --init
If you try to use the script without the .gitsync.json
file present in the home folder, you will be prompted to initialize it, and execution will continue after the file is created.
Initializes/updates git credentials
Kind: Exported function
Returns: Promise
- Resolves to the the output of fs.writeFile or to message: 'Credentials not updated'
Param | Type | Default | Description |
---|---|---|---|
[cred] | object |
{} |
Credentials to keep Reads file with credentials, prompts for creation if not found and for update if found. Creates/Updates credentials. |
Gets all user's or org's repos names
Kind: Exported function
Returns: repos
- Mapped to have attributes name, full_name, local_path
Param | Type | Description |
---|---|---|
name | string |
Github username |
org | boolean |
Whether the account belongs to an organization |
user | string |
User-Agent Header |
at | string |
Github authentication token |
Checks for validity of path, must be string and satisfy
Kind: Exported function
Returns: boolean
- Whether path is valid
Param | Type | Description |
---|---|---|
path | string |
Path under which to clone a repo |
Clones a repo in path specified if path is valid. Else, clones to cwd
Kind: Exported function
Returns: Promise
- Resolves to the path under which the repo was cloned
Param | Type | Description |
---|---|---|
repo | object |
Repository info |
repo.name | string |
|
repo.full_name | string |
|
repo.local_path | string |
local path to which the repo will be cloned |
at | string |
Github authentication token |
Finds all repository folder paths under cwd. Used to update repos status
Kind: Exported function
Returns: Array.<string>
- The repository folder paths under cwd
Updates refs for cwd
Kind: Exported function
Returns: string
- Repo status: diverged, fast-forward, up-to-date
Param | Type | Description |
---|---|---|
path | string |
The absolute path to use as an cwd with exec |
Pulls all branches for repo
Kind: Exported function
Returns: string
- Success message
Param | Type | Description |
---|---|---|
path | string |
The absolute path to use as an cwd with exec |
Returns all repo branches
Kind: Exported function
Returns: Array.<string>
- The branch names
Param | Type | Description |
---|---|---|
path | string |
The absolute path to use as an cwd with exec |
Creates local branches production and branches with prodv prefix, if not found
Kind: Exported function
Returns: Array.<string>
- The branches that were added
Param | Type | Description |
---|---|---|
path | string |
The absolute path to use as an cwd with exec |
branches | Array.<string> |
All repo branches |