Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cli: add support for actions in popper search #485

Closed
ivotron opened this issue Feb 12, 2019 · 2 comments
Closed

cli: add support for actions in popper search #485

ivotron opened this issue Feb 12, 2019 · 2 comments

Comments

@ivotron
Copy link
Collaborator

ivotron commented Feb 12, 2019

Bring back the functionality of the popper search command so that it is able to index and search actions contained in a pre-defined list of repositories (e.g. all repositories in the popperized organization). This list of repositories containing actions is written in the .popper.yml file and can be modified by the user

@ivotron ivotron changed the title cli: add support for stages in popper search cli: add support for actions in popper search Feb 16, 2019
@JayjeetAtGithub
Copy link
Collaborator

@ivotron Will the popper search functionality in popper 2.0 be the same as that of popper 1.x ?

@ivotron
Copy link
Collaborator Author

ivotron commented Mar 25, 2019

Yes, the idea is to allow users to do popper search <keyword> so that they can search for actions by matching the given keyword to the name of an action. An --include-readme flag then instructs popper to search also by looking at the content of the README file.

A list of action repos is defined in a search_sources attribute of the .popper.yml file. For example:

search_sources:
- github.com/popperized/zenodo
- github.com/popperized/cloudlab
- github.com/actions/aws
- github.com/actions/gcloud
..

We can have a list of repos specified by default. An alternative would be to have that list be defined in a repo, and retrieve it everytime we do a popper search --update-sources. This latter can be left out of the scope of this issue (we might want to create a separate issue for that).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants