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
I'm not actually sure how CI was set up initially but tests are no longer being run. This repo is also still using bors, which is no longer a thing. It's possible that reinstating CI could be as simple as swapping bors for GitHub Actions but I'm unsure and haven't looked into it at all.
EDIT: Okay I looked into it briefly, the tests are running (and passing) on cron, I think we just need to enable them to run on PRs in the GHA config?
The text was updated successfully, but these errors were encountered:
xref JuliaCloud/AWS.jl#630, where it was discussed how to use the "require approval for new contributors" setting to gate access to real-s3 which I think we'd want to do here
xref JuliaCloud/AWS.jl#630, where it was discussed how to use the "require approval for new contributors" setting to gate access to real-s3 which I think we'd want to do here
I've dropped bors being a required check before merging, we already had it but confirming that 1st time contributors require approval for CI runs.
I'm not actually sure how CI was set up initially but tests are no longer being run. This repo is also still using bors, which is no longer a thing. It's possible that reinstating CI could be as simple as swapping bors for GitHub Actions but I'm unsure and haven't looked into it at all.
EDIT: Okay I looked into it briefly, the tests are running (and passing) on cron, I think we just need to enable them to run on PRs in the GHA config?
The text was updated successfully, but these errors were encountered: