Skip to content
This repository has been archived by the owner on Jul 26, 2024. It is now read-only.

Try set up CS GitHub Action #61

Merged
merged 8 commits into from
Apr 12, 2021
Merged

Try set up CS GitHub Action #61

merged 8 commits into from
Apr 12, 2021

Conversation

admturner
Copy link
Member

@admturner admturner commented Apr 12, 2021

Description

The plan is to replace Travis CI with GitHub Actions. This is the first attempt at that. It should replace all of the Travis CI coding standards linting (for JS, CSS, JSON, and PHP) with equivalent jobs in GitHub Actions. This will fix #60.

How has this been tested?

Types of changes

  • Add GitHub Actions workflow config.
  • Remove Travis CI config.

Checklist:

  • My code is tested.
  • My code follows the WordPress code style.
  • My code follows the accessibility standards.
  • My code has proper inline documentation.
  • I've included developer documentation if appropriate.

@admturner admturner self-assigned this Apr 12, 2021
@admturner admturner added the build tooling Build tools. label Apr 12, 2021
@admturner admturner added this to the 1.0.0 milestone Apr 12, 2021
Hit issues with package lock file version warning and `fsevents`
error. Attempted running with `npm install` instead of `npm ci`,
with no effect. In a separate branch rebuilt `package-lock.json`
because problem might have related to using a lock file that had
been built for a different version of npm.
@admturner admturner merged commit 2817e66 into develop Apr 12, 2021
@admturner admturner deleted the tools/use-github-actions branch April 12, 2021 18:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
build tooling Build tools.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Switch from Travis CI to GitHub Actions
1 participant