leko / git-upstream

Utility to set the remote "upstream" on forked repository

git-upstream

Utility to set the remote "upstream" on forked repository.

Usage

Options:
  --help       Show help                                               [boolean]
  --version    Show version number                                     [boolean]
  --set, -i    Set upstream to a remote               [boolean] [default: false]
  --force, -f  Force overwrite even if upstream already exists
                                                      [boolean] [default: false]
  --token, -t  GitHub access token for private repository               [string]
  --shallow    Prefer parent fork(default) or ancestor fork
                                                       [boolean] [default: true]
  --https      Set https url to remote, otherwise set ssh url
                                                      [boolean] [default: false]

Examples:
  npx git-upstream                     Show upstream url
  npx git-upstream --set               Set upstream with confirmation
  npx git-upstream --set -f            Set upstream even if upstream already
                                       exists
  npx git-upstream --set --https       Set https://...
  npx git-upstream --set --no-shallow  For deep nested fork

Contribution

1. Fork this repository
2. Write your code
3. Run tests
4. Create pull request to master branch

Development

git clone [email protected]:Leko/git-upstream.git
cd git-upstream
npm i

License

This package under MIT license.

git-upstream's Issues

An in-range update of @octokit/rest is breaking the build 🚨

The dependency @octokit/rest was updated from 16.28.8 to 16.28.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci: node-v8: Your tests failed on CircleCI (Details).
• ❌ ci/circleci: node-v10: Your tests failed on CircleCI (Details).
• ❌ ci/circleci: node-v12: Your tests failed on CircleCI (Details).
• ❌ ci/circleci: node-latest: Your tests failed on CircleCI (Details).

---

Release Notes for v16.28.9

16.28.9 (2019-09-03)

Bug Fixes

• package: update universal-user-agent to version 4.0.0 (b5a96a9)

Commits

The new version differs by 3 commits.

• ee57e51 refactor: adapt for universal-user-agent@v4
• 981597d chore(package): update lockfile package-lock.json
• b5a96a9 fix(package): update universal-user-agent to version 4.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Omit lodash

src/index.js:3:const flow = require("lodash/flow");
src/index.js:106:  .then(flow(chalk.cyan, console.log))
src/index.js:108:    flow(

An in-range update of yargs is breaking the build 🚨

The dependency yargs was updated from 13.2.2 to 13.2.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

yargs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci: node-v10: Your tests failed on CircleCI (Details).
• ❌ ci/circleci: node-v8: Your tests failed on CircleCI (Details).
• ❌ ci/circleci: node-latest: Your tests failed on CircleCI (Details).

---

Commits

The new version differs by 14 commits.

• a6e67f1 chore(release): 13.2.4
• fc13476 chore: update standard-verison dependency
• bf46813 fix(i18n): rename unclear 'implication failed' to 'missing dependent arguments' (#1317)
• a3a5d05 docs: fix a broken link to MS Terminology Search (#1341)
• b4f8018 build: add .versionrc that hides test/build
• 0c39183 chore(release): 13.2.3
• 08e0746 chore: update deps (#1340)
• 843e939 docs: make --no- boolean prefix easier to find in the docs (#1338)
• 84cac07 docs: restore removed changelog of v13.2.0 (#1337)
• b20db65 fix(deps): upgrade cliui for compatibility with latest chalk. (#1330)
• c294d1b test: accept differently formatted output (#1327)
• ac3f10c chore: move .hbs templates into .js to facilitate webpacking (#1320)
• 0295132 fix: address issues with dutch translation (#1316)
• 9f2468e doc: clarify parserConfiguration object structure (#1309)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of @octokit/rest is breaking the build 🚨

The dependency @octokit/rest was updated from 16.22.0 to 16.23.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci: node-v8: CircleCI is running your tests (Details).
• ❌ ci/circleci: node-v10: CircleCI is running your tests (Details).
• ❌ ci/circleci: node-latest: Your tests failed on CircleCI (Details).

---

Release Notes for v16.23.0

16.23.0 (2019-04-02)

Features

• options.auth can be set to token without a prefix (736174e)

Commits

The new version differs by 7 commits.

• 736174e feat: options.auth can be set to token without a prefix
• 0e7ee78 build(package): atob-lite
• a9e8fca docs(README): remove optional authorization prefixes from code examples
• 7ec21b1 test: options.auth function returning string without basic/token/bearer prefix
• 1a9d73a test: options.auth set to string without basic/token/bearer prefix
• 1661493 build(package): lock file update
• 48edead chore(package): update @octokit/routes to version 19.1.1

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Error: octokit.authenticate() is deprecated. Use "auth" constructor option instead

Error: octokit.authenticate() is deprecated. Use "auth" constructor option instead.
    at authenticate (/home/lekonoor/.npm/_npx/5879/lib/node_modules/git-upstream/node_modules/@octokit/rest/plugins/authentication-deprecated/authenticate.js:4:26)
    at main (/home/lekonoor/.npm/_npx/5879/lib/node_modules/git-upstream/index.js:16:13)
    at Object.<anonymous> (/home/lekonoor/.npm/_npx/5879/lib/node_modules/git-upstream/index.js:105:1)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
    at findNodeScript.then.existing (/home/lekonoor/.nvm/versions/node/v10.15.0/lib/node_modules/npm/node_modules/libnpx/index.js:268:14)

Deprecation warning for Octokit/rest

When I was running npx git-upstream -set, I got the following warning.

[@octokit/rest] `const Octokit = require("@octokit/rest")` is deprecated. Use `const { Octokit } = require("@octokit/rest")` instead