yes, please update PR #3 with new implementation matching the spec above @shoko
kugetsu could support multiple git server instances, and the example right now is sufficient.
default fallback from the kugetsu init should always refer to github.com, but yes its should be…
instead of creating a new kugetsu file, is it makes sense to modify the existing kugetsu file inside kugetsu/skills/kugetsu/scripts/kugetsu? what do you think?
for data directory location I'm thinking at ~/.jigaido/*, what do you think?
I don't understand cross-group bounty lookup, Group A should only be accessible within Group A. no individual or…
KUGETSU_VERBOSITY should be in the config file as well, refer to #69
I think we should include in kugetsu initialize that it will write config file. so basically its easier for user to modify it rather than figuring out which config key is it. we initialized the…
git.fbrns.co/shoko/kugetsu#
it keeps saying git.fbrns.co/shoko/kugetsu#, we want these to be dynamic. in a way that, git server domain can change. it can be gitlab.com,…
I think PM can ONLY write to:
~/.kugetsu/queue.json- Queue state~/.kugetsu/logs/*- Your logs
the rest, PM can read but not write. what do you think?
also for point 27 when…
yes pm is expected to modify files inside ~/.kugetsu, its our core features so that pm can manage issues, polling, delegation, etc. what pm shouldn't do is write in another files, such as…
I heard that changing sh -c to bash -c introduce a new error. can you check?
if PM session dead, and command fails silently in background, it will just confusing. what are the options to handle this? should we have log or something somewhere so all the delegation can pick…