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

Switch to GitHub Actions for CI and Deployment #97

Merged
merged 12 commits into from Apr 16, 2020
Merged

Conversation

michaelweylandt
Copy link
Member

  • Move to GitHub Actions for CI and Deployment, as recommended
    by tidyverse / r-lib teams

    GHA provides more concurrent builds, longer build time limits,
    and smoother integration with GitHub

  • Remove .travis.yml and replicate logic in .github/workflows/check.yml

  • Tweaks to .gitignore and .Rbuildignore as needed

- Move to GitHub Actions for CI and Deployment, as recommended
  by tidyverse / r-lib teams

  GHA provides more concurrent builds, longer build time limits,
  and smoother integration with GitHub

- Remove .travis.yml and replicate logic in .github/workflows/check.yml
- Tweaks to .gitignore and .Rbuildignore as needed
- Add packages used for testing to Suggests
- Check scalar-ness before checking positivity
  to avoid inappropriate logical recycling
- Add useDynLib call to NAMESPACE stump to avoid triggering error
  from .onLoad methods
- Remove roxygen note from DESCRIPTION file
- Declare unnesting columns explicitly, as required
  by new versions of tidyr
- Per CRAN rules, update ArXiv link format
- Per CRAN rules, don't include package name in description
- Explicitly name sp.path object in sparsity analysis
  (sp.path is the indicator of edge fusions)
  so as_tibble() doesn't need to automatically name
  (which throws a warning)
- Change NA tests to anyNA to ensure a scalar
  value in if() statements
- Use inherits instead of class() ==
- Use identical instead of == to avoid possible length problem
- Fix logical recycling error in cbass.R
- This is failing on GitHub CI with the error message:

      argument 'fps' must be a factor of 100

  (coming from the magick package) but it succeeds locally.

  CI should be installing the (preferred) gifski renderer so
  it's unclear why ImageMagick is being used at all, but
  it's not a blocker for now.
- Add check for autodeployment from `develop` branch
  only (not PRs)
- Move build status badge from TravisCI to GitHub Actions
- Remove AppVeyor Badge
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant