-
Notifications
You must be signed in to change notification settings - Fork 24
chore: refactor ci #622
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
chore: refactor ci #622
Conversation
Signed-off-by: Taylor Price <[email protected]>
username: ${{ secrets.GHCR_USERNAME }} | ||
password: ${{ secrets.GHCR_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this? Can we use the token passed to the action?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm.. we probably could get rid of these yeah. ill follow up on that in a separate set of prs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question here about using the GitHub token passed to the action instead of a secret.
cd /obot-tools | ||
|
||
if [ ! -e workspace-provider ]; then | ||
git clone --depth=1 https://github.com/gptscript-ai/workspace-provider |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: would be nice to be able to change these with an env var or something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah ive got that marked down as a future enhancement
Signed-off-by: Taylor Price [email protected]