In November of 2023 we moved to using GitHub Actions instead of CircleCI. This PR reorganizes a couple of things so that scripts referenced by the GitHub Actions and CircleCI workflows are located in a common directory (bin) and so that scripts used only by CircleCI are located in the .circleci directory.
I had considered removing the .circleci directory entirely, but decided against it because downstream developers may be using CircleCI and it would be kind of rude to clobber their configs. I'd be interested in hearing from folks what they think on this point. Maybe in the future we could remove the CircleCI config as a kind of "deprecation removal" as part of a major version release.
In November of 2023 we moved to using GitHub Actions instead of CircleCI. This PR reorganizes a couple of things so that scripts referenced by the GitHub Actions and CircleCI workflows are located in a common directory (
bin) and so that scripts used only by CircleCI are located in the.circlecidirectory.I had considered removing the
.circlecidirectory entirely, but decided against it because downstream developers may be using CircleCI and it would be kind of rude to clobber their configs. I'd be interested in hearing from folks what they think on this point. Maybe in the future we could remove the CircleCI config as a kind of "deprecation removal" as part of a major version release.