Mamading Ceesay
Mamading Ceesay
Have been using `repoxplorer-github-organization`. So a `--skip-repos` option would definitely be very helpful here.
Had incorporated `repoxplorer-github-organization` into a cronjob. As a workaround, I'm going to stop running the cronjob for the relevant organzation and edit out the offending repo from the definition file....
> > Yes that makes sense but you won't benefit the automatic update if a new repo appears in your org. > […](#) Yep, that's why I referred to it...
Looks like I'm going to be hacking on `repoxplorer-github-organization` a bit. See #62. So I might end up adding `--skip-repos` myself at some point, if I still have a need...
Yeah, was looking into this last night and came across this: https://stackoverflow.com/questions/18683810/docker-supervisord-and-logging-how-to-consolidate-logs-in-docker-logs Will try implementing *supervisor-stdout*.
Okay, that might be an option for me. Any suggestions as to where in the code I should be looking to do this?
Thanks will take a look.
So I'm thinking of adding some sort of directive either in `config.py` or the definitions file to act as a flag for not showing commits for a given organization. Bonus...
Fixes #1357 which duplicates #157
I'm having this exact issue with [flan-alpaca-xl](https://huggingface.co/declare-lab/flan-alpaca-xl).