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
So this is just documenting mu thought process around this.
Given you can clone a user and it automatically looks for user's in github.com/username/dot-aliases
Example command/usage"
aliases search git commit introduced string
This under the covers makes an external request to an aliases search server which caches all known external aliases and returns results that match the query string.
How does the cache get built?
When a user aliases clone successfully a ping is sent to the aliases search server to index that user.
What does the search search use as search data?
It uses all the current data about an alias but we also add a description field to allow for free text.
What can a user do once they have found an alias they want to use?
Copy it locally
straight copy of the alias to a local user/directory
Clone it
clone the user's alias and there can a further update process that can keep it in sync, with prompts to confirm as this could be dangerous.
Use it once
maybe copy it to clipboard or something
The text was updated successfully, but these errors were encountered:
Proposal: aliases search
So this is just documenting mu thought process around this.
Given you can clone a user and it automatically looks for user's in
github.com/username/dot-aliases
Example command/usage"
This under the covers makes an external request to an aliases search server which caches all known external aliases and returns results that match the query string.
How does the cache get built?
When a user
aliases clone
successfully a ping is sent to the aliases search server to index that user.What does the search search use as search data?
It uses all the current data about an alias but we also add a
description
field to allow for free text.What can a user do once they have found an alias they want to use?
The text was updated successfully, but these errors were encountered: