😄 About the Project

✋ Contribution

1. Fork the project. (https://github.com/tamada/rrh/fork)
2. Create a feature branch. (git checkout -b FEATURE_BRANCH_NAME)
3. Edit the source files and Commit your changes.
4. Create tests and commit them.
5. Rebase your local changes against the master branch.
6. Run the test suite with the make test and confirm that passes.
7. Create a new pull request.
8. Confirm all checks pass.

📗 Code of Conduct

📜 License

Apache License version 2.0

💬 Discussion

Join our Gitter channel if you have any problem or suggestions to rrh.

For Japanese user, misc_ja channel has discussions in Japanese. The public language of other channels and GitHub project pages are English.

👥 Authors

❓ Why the project name RRH

At first, the name of this project was GRIM (Git Repository Integrated Manager). However, the means of grim is not good, and there are many commands which start with gr. Therefore, we changed the project name to rrh. RRH means “Repositories, Ready to Hack” or “Remote Repositories Head,” are not the abbreviation of the Red Riding Hood.

🤝 Attributions

Icon of RRH

by iconpon.com

🐾 Version histories

• v1.2.0 (24 Apr, 2020)
  • #83 (introduce rrh open sub command)
• v1.1.0 (18 Dec, 2018)
  • #79 (add rrh group info sub command)
  • #77 (introduce rrh repository update-remotes sub command)
  • #81 (introduce options for rrh prune command)
• v1.0.4 (13 Jul, 2018)
  • #74 (permission of created README.md by rrh-new was invalid (204))
  • #75 (Introduce --dry-run option to rrh new command)
• v1.0.3 (29 Jun, 2018)
  • #72 (Print belonging groups on rrh repository info)
• v1.0.2 (29 Jun, 2018)
  • #67 (implements rrh new sub command)
• v1.0.1 (26 Jun, 2018)
  • #68 (rrh group prints rrh config list)
• v1.0.0 (18 Jun, 2018)
  • The first public release.