juancrg90 / vpr

VPR is a CLI that helps you to quickly manage your project in GitHub/GitLab/Bitbucket

vpr

VPR is a CLI that helps you to quickly manage your project in GitHub/GitLab/Bitbucket. You can visit with ease different project sections, like the issues page, a specific commit, create pull requests (merge requests for GitLab), and more, also is configurable for other platforms PRs are open.

Installation

  $ gem install vpr

Usage

All the commands use the URL set as origin in your git remote to perform the web request, you can use the flag --remote=REMOTE to specify which service you want to visit if you have your project stored in more than one platform.

vpr branch

Open in your browser your current branch.

vpr branches

Open the page that shows the uploaded branch list.

vpr help

Show the likst of available vpr commands, you can pass an specific command to get more details.

vpr home

Open in your browser the project page.

vpr issues

Open the in your browser issues list page.

vpr pull

Create a new pull request or visit an existing one for the current branch.

vpr pulls

Open the pull requests list page.

vpr search COMMIT

Search a given commit in the project page. the behavior of this command depends of the plaftorm, for example GitHub search in code, issues an PRs.

vpr visit COMMIT

Open in the browser the page with the commit passed as an argument.

vpr version

Show the current vpr version

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/JuanCrg90/vpr. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Vpr project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

vpr's Issues

Add linter/formatter GitHub action

I noticed you aren’t using a linter/formatter like rubocop or standardRB. Would you be interested in adding one?

If so I can hook up a GitHub action for you. Check out this repo for an example of actions I have created.

Add support vpr pulls in gitlab

update

vpr pulls

to support gitlab

examples:

GitHub:
https://github.com/JuanCrg90/vpr/pulls

This is similar to #19

Allow to use vpr even if you are not in the root directory

Currently vpr only can be used in the project root directory where .git directory lives.

Traceback (most recent call last):
/Users/juancarlosruiz/project/app/models/.git: path does not exist (ArgumentError)

Update the behavior to look for .git directory in the parent directories

CI is broken

Add support vpr pull in bitbucket

The route for pull requests in bit bucket is different to the github endpoint

Analyze if is possible to map the pull request endpoint like in github

command to update

vpr pull

Add support vpr pull in gitlab

Analyze if is possible to map the merge request endpoint like in github

command to update

vpr pull

This is similar to #9

Add support vpr branch in gitlab

update

vpr branch

to support gitlab

examples:

GitHub:
https://github.com/JuanCrg90/vpr/tree/master

This is similar to #18

Add support vpr search in bitbucket

The route for commit search in bitbucket is different to the GitHub endpoint

update

vpr search <commit>

to support bitbucket

examples:

Github
https://github.com/JuanCrg90/vpr/search?q=ff1018601

bitbucket
https://bitbucket.org/JuanCrg90/vpr/commits/?search=ff1018601

Improve the Readme

Currently, the readme only talks about GitHub and has a lot of (maybe) unnecessary gifs. It's necessary update it to include information about bitbucket and gitlab.

vpr pull fails on renamed repos

vpr pull fails when a repo has been renamed. I would be nice try to find a way to handle this error

Add vpr --version command

Add vpr --version to show the installed CLI version

Add support to select remote branch to visit

Currently when you run a vpr command this send you to the origin remote

Add a flag to select which remote you want to use

vpr --remote=upsteam visit 12abcd

Add support vpr branch in bitbucket

The route for branches in bitbucket is different to the GitHub endpoint

update

vpr branch

to support bitbucket

examples:

GitHub:
https://github.com/JuanCrg90/vpr/tree/master

bitbucket
https://bitbucket.org/JuanCrg90/vpr/branch/master

Add support vpr pulls in bitbucket

The route for pull requests index in bitbucket is different to the GitHub endpoint

update

vpr pulls

to support bitbucket

examples:

GitHub:
https://github.com/JuanCrg90/vpr/pulls

bitbucket
https://bitbucket.org/JuanCrg90/vpr/pull-requests