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
There is circle-ci setup cloned along.
I bet it is easy, but I never dealt with setting up circle ci for a repo so I would appreciate if someone else (@satra?) would do it so we get PRs and on cron tested here.
The text was updated successfully, but these errors were encountered:
How about we enable Circle-CI for now, until someone sets up github actions? @dchiquit had merged some PRs that didn't lint or pass tests in dandi-api repo, and we don't want to do that in the future. Enabling circle should be very quick as there is already a config file.
What is the reason to move from Circle to GitHub actions @satra (as referenced in #1) ?
I myself don't have a strong preference--as long GitHub actions can give us what we get from circle--other than getting CI setup ASAP and circle is already most of the way there (and our config is debugged) for this repo.
There is circle-ci setup cloned along.
I bet it is easy, but I never dealt with setting up circle ci for a repo so I would appreciate if someone else (@satra?) would do it so we get PRs and on cron tested here.
The text was updated successfully, but these errors were encountered: