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
This issue pertains to ads-github-fetch-all-upstreams as included in ads-github-tools-0.2.0.
It is not uncommon that there is a problematic repo (or three) that you want the ads-github-fetch-all-upstreams tool to ignore (for whatever reason). The only way to accomplish that with the current version of the codebase (0.2.0) is to explicitly list on the command line the repos that you wish to operate on; this becomes cumbersome when dealing with a large number of repos, and more so when you are working with more repos than can be named on the command line (e.g., due to system exec*() (E2BIG)):
It would be nice if there were one more more command line options to exclude certain repos (analogous to GNU grep's options --exclude=GLOB, --exclude-from=FILE, and --exclude-dir=GLOB). An improvement beyond that would be to also support an "ignore" file (possibly multiple), similar to the way .gitignore files work.
The text was updated successfully, but these errors were encountered:
This issue pertains to
ads-github-fetch-all-upstreams
as included in ads-github-tools-0.2.0.It is not uncommon that there is a problematic repo (or three) that you want the
ads-github-fetch-all-upstreams
tool to ignore (for whatever reason). The only way to accomplish that with the current version of the codebase (0.2.0
) is to explicitly list on the command line the repos that you wish to operate on; this becomes cumbersome when dealing with a large number of repos, and more so when you are working with more repos than can be named on the command line (e.g., due to systemexec*()
(E2BIG
)):or, more perhaps more readably:
It would be nice if there were one more more command line options to exclude certain repos (analogous to GNU
grep
's options--exclude=GLOB
,--exclude-from=FILE
, and--exclude-dir=GLOB
). An improvement beyond that would be to also support an "ignore" file (possibly multiple), similar to the way.gitignore
files work.The text was updated successfully, but these errors were encountered: