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
Repository names can often collide and require some "namespacing", e.g. Foo/plugins and Bar/plugins (which I would locally name foo-plugins and bar-plugins). They can also sometimes be unreasonably long like LongRepositoryNameGeneratorFactoryFactory, which I'd name long-repo-name-generator or something.
Would you be interested in a PR that adds aliasing? It would probably be a simple key-value table, with org/repo as the key, and path/to/repo as the value (resulting in /home/changeMe/path/to/repo, or, if an absolute path, /path/to/repo).
The text was updated successfully, but these errors were encountered:
Repository names can often collide and require some "namespacing", e.g.
Foo/plugins
andBar/plugins
(which I would locally namefoo-plugins
andbar-plugins
). They can also sometimes be unreasonably long likeLongRepositoryNameGeneratorFactoryFactory
, which I'd namelong-repo-name-generator
or something.Would you be interested in a PR that adds aliasing? It would probably be a simple key-value table, with
org/repo
as the key, andpath/to/repo
as the value (resulting in/home/changeMe/path/to/repo
, or, if an absolute path,/path/to/repo
).The text was updated successfully, but these errors were encountered: