Change Details

Hello Hashar, thank you for your hard work on quibble, awesome work. We are planning on establishing local testing environment and really like quibble. Problem we have is that not all of our code is located on Gerrit, and we were thinking of a possiblity to have quibble work with another backend. I can see that the URL for the repo is constructed of base URL [ [[ https://github.com/wikimedia/quibble/blob/master/quibble/zuul.py#L53 | 1 ]] ] and ZUUL_PROJECT/EXT_DEPENDENCIES in [ [[https://github.com/wikimedia/quibble/blob/master/quibble/zuul.py#L53|2]] ]. We can define those in .env file. We would also need to make [ [[https://github.com/wikimedia/quibble/blob/master/quibble/cmd.py#L197-L198|3]] ] configurable in order to specify the mediawiki-core name. We would very much appreciate your opinion on whether this is a worthwhile effort and a good idea or is quibble too specificly tied to gerrit. Thank you

Hello Hashar, thank you for your hard work on Quibble, awesome work. We are planning on establishing local testing environment and really like quibble. Problem we have is that not all of our code is located on Gerrit, and we were thinking of a possiblity to have quibble work with another backend. I can see that the URL for the repo is constructed of base URL [ [[ https://github.com/wikimedia/quibble/blob/6878b6271c6b3fb72b485e1b382fff15b8389df9/quibble/zuul.py#L53 | 1 ]] ] and ZUUL_PROJECT/EXT_DEPENDENCIES in [ [[https://github.com/wikimedia/quibble/blob/6878b6271c6b3fb72b485e1b382fff15b8389df9/quibble/zuul.py#L53|2]] ]. We can define those in .env file. We would also need to make [ [[https://github.com/wikimedia/quibble/blob/6878b6271c6b3fb72b485e1b382fff15b8389df9/quibble/cmd.py#L197-L198|3]] ] configurable in order to specify the `mediawiki/core` repository name. We would very much appreciate your opinion on whether this is a worthwhile effort and a good idea or is quibble too specificly tied to gerrit. Thank you

Hello Hashar, thank you for your hard work on qQuibble, awesome work. We are planning on establishing local testing environment and really like quibble. Problem we have is that not all of our code is located on Gerrit, and we were thinking of a possiblity to have quibble work with another backend. I can see that the URL for the repo is constructed of base URL [ [[ https://github.com/wikimedia/quibble/blob/master6878b6271c6b3fb72b485e1b382fff15b8389df9/quibble/zuul.py#L53 | 1 ]] ] and ZUUL_PROJECT/EXT_DEPENDENCIES in [ [[https://github.com/wikimedia/quibble/blob/master6878b6271c6b3fb72b485e1b382fff15b8389df9/quibble/zuul.py#L53|2]] ]. We can define those in .env file. We would also need to make [ [[https://github.com/wikimedia/quibble/blob/master6878b6271c6b3fb72b485e1b382fff15b8389df9/quibble/cmd.py#L197-L198|3]] ] configurable in order to specify the `mediawiki-core/core` repository name. We would very much appreciate your opinion on whether this is a worthwhile effort and a good idea or is quibble too specificly tied to gerrit. Thank you