chris-rock/git-issues

Interact with git issues on Bitbucket and GitHub on CLI

git-issue

• list issues (bitbucket ✔, github ✔, gitlab ✔)
• create issue (bitbucket ✔, github ✔, gitlab ✔)
• delete issue (bitbucket ✔, github ✔ (n/a), gitlab ✔ (n/a))
• cli integration ⋯

Why? There's excellent tools for GitHub out there, but I found integration for BitBucket or Gitlab lacking.

Installation

You can build the gem and install it on your system:

bundle install
bundle exec gem build git-issues.gemspec
bundle exec gem install *gem

Security

Your login information will be stored by default in: ~/.git-issues.conf. Make sure to keep this file's permissions limited (e.g. 0600).

If you can, do not use username and password for login. Use OAuth instead. If you use username and password, both will be stored in the configuration file in an unencrypted state, which is highly discouraged.

How to get OAuth tokens:

• GitHub: Go to Account Settings, Applications, and click on Create a new Personal Access Token. Enter git-issues as the description. Use this token during first login.
• OAuth on BitBucket
• Gitlab: Click on your profile, Profile Settings, Account and use the Private token found here.

Contributing

Any contributions are welcome!

1. Fork the repository on Github
2. Create a named feature branch (like add_component_x)
3. Write you change
4. Write tests for your change (if applicable)
5. Run the tests, ensuring they all pass
6. Submit a Pull Request using Github

License and Author

Author: Dominik Richter [email protected]

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and