-
Notifications
You must be signed in to change notification settings - Fork 60
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: extend 'uses' keyword for action blocks to handle any Git repo (as opposed to just Github's) #483
Comments
Using these REST APIs might require defining some place to save auth details for these. Probably somewhere separate from |
@eltrufas thanks for the feedback! At some point the |
Gave this a bit more of thought, I've updated the title and description as a result. It simplifies things as we don't need to use a REST API anymore (we do everything through Git) |
Hey ivo, i have an issue, im not sure how to handle urls from different services. Before we could do user/repo/dir-path but now im not sure how to handle a generic git url without breaking back compatibility. Here is my code: https://github.com/barbaraDorame/popper/tree/issue-483 Thanks in advance! |
hey @barbaraDorame , I left some comments on barbaraDorame@ac75e00 . Please take a look |
Extends the interpretation of the 'uses' attribute of action blocks so that other Git URLs besides those pointing to Github are allowed. fixes #483
Extends the interpretation of the 'uses' attribute of action blocks so that other Git URLs besides those pointing to Github are allowed. fixes #483
Extends the interpretation of the 'uses' attribute of action blocks so that other Git URLs besides those pointing to Github are allowed. fixes #483
Extends the interpretation of the 'uses' attribute of action blocks so that other Git URLs besides those pointing to Github are allowed. fixes #483
Extend the
uses
keyword of action blocks so that users can provide arbitrary Git URLs. The format would be:or
The text was updated successfully, but these errors were encountered: