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

Implement at least minimal *automatic* CI #2593

Open
cebtenzzre opened this issue Jul 8, 2024 · 1 comment · May be fixed by #2688
Open

Implement at least minimal *automatic* CI #2593

cebtenzzre opened this issue Jul 8, 2024 · 1 comment · May be fixed by #2688
Assignees
Labels
backend gpt4all-backend issues chat gpt4all-chat issues circleci circleci pipeline issues python-bindings gpt4all-bindings Python specific issues

Comments

@cebtenzzre
Copy link
Member

Currently, the only CI that runs automatically on PRs, even those submitted by people with write access to this repo, is a spell check.

We should at least have a check to make sure that code submitted to this repo compiles on one of macOS, Windows, or Linux. Better, all of them. Even better, we could test basic functionality of the backend and python bindings automatically.

@cebtenzzre cebtenzzre added backend gpt4all-backend issues python-bindings gpt4all-bindings Python specific issues circleci circleci pipeline issues chat gpt4all-chat issues labels Jul 8, 2024
@manyoso manyoso assigned manyoso and johnwparent and unassigned manyoso Jul 11, 2024
@manyoso
Copy link
Collaborator

manyoso commented Jul 17, 2024

I would like this implemented with github actions I think and could be the first in an effort to move all of our CI to github actions.

@johnwparent johnwparent linked a pull request Jul 17, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend gpt4all-backend issues chat gpt4all-chat issues circleci circleci pipeline issues python-bindings gpt4all-bindings Python specific issues
Projects
Status: Short-Term Priority List
Development

Successfully merging a pull request may close this issue.

3 participants