You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to be able to add additional repositories to the BL gallery. This would aid people that want to maintain their own versions, but also make it easier to test changes before merging them to master. I'm aware that you can use 'local' templates, but this doesn't solve all these problems.
One other option would be to support 'local repositories insame manner as the GitHub repos, this would be an extension to the current local templates support.
The text was updated successfully, but these errors were encountered:
we could add a section in "user settings" for this. either override the branch for the BL-data repo, or add forked repos collection. Having a consistent repo layout would be key as reading any old repo could prove problematic. But a fork of BL-data could work well.
I really think this would be useful to be honest and like your suggestion. Although ideally multiple repositories, i.e. default and others? A key to this would be using private repos too, i.e. with credentials as some people have scripts and sensitive info in scripts that they can't make public.
So I didn't really get this then, but I think the idea here is that people fork the batchlabs-data repo and use that version as the data source? We already added the option to change the branch so shouldn't be much changes to also support changing the github user
It would be great to be able to add additional repositories to the BL gallery. This would aid people that want to maintain their own versions, but also make it easier to test changes before merging them to master. I'm aware that you can use 'local' templates, but this doesn't solve all these problems.
One other option would be to support 'local repositories insame manner as the GitHub repos, this would be an extension to the current local templates support.
The text was updated successfully, but these errors were encountered: