Skip to content
This repository has been archived by the owner on Oct 30, 2024. It is now read-only.

Script to speed up setting of gitbz configurations #257

Open
alexklbuckley opened this issue Mar 22, 2018 · 3 comments
Open

Script to speed up setting of gitbz configurations #257

alexklbuckley opened this issue Mar 22, 2018 · 3 comments

Comments

@alexklbuckley
Copy link

A script to make the process of setting git bz configs faster and easier for new users.

This script will run the following commands:
git config bz.default-tracker bugs.koha-community.org
git config bz.default-product Koha
git config --global bz-tracker.bugs.koha-community.org.path /bugzilla3

git config --global bz-tracker.bugs.koha-community.org.https true
git config --global core.whitespace trailing-space,space-before-tab
git config --global apply.whitespace fix

It will also prompt the user to write in their Koha bugzilla username and password.

@alexklbuckley
Copy link
Author

https://github.com/alexklbuckley/kohadevbox/tree/kohadevbox2_work --This branch of kohadevbox forked repo contains the configurebzconfigs.sh script which does the above

@tomascohen
Copy link
Contributor

Alex, this is currently handled by cars/user.yml

@alexklbuckley
Copy link
Author

Hi Tomas

Because vars/user.yml is a yaml configuration file rather than an executable file it still requires you to go in and manually add your details and uncomment lines. Would it be useful if I amended the script I wrote so that it edits the vars/user.yml for you when running it after writing in your details to the terminal.

The reason we think this script automating the process of setting the bugzilla configs is we did a user group for Koha users a few weeks ago and did a bug fixing session for users with a variety of experience and knowledge and we came to the conclusion that running a script which you just enter your Bugzilla username and password into would be easier for a total beginner library user who would like to start out contributing to Koha, rather than them having to go into a config file and edit it.

Cheers,
Alex

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants