Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Issues
  • #20466
Closed
Open
Issue created Aug 04, 2016 by Administrator@rootContributor

Hound warnings on JS test files

Created by: maxbeatty

I've opened a few PRs and each gets lots of comments from @houndci-bot because the JS unit test files do not conform to the ESLint settings. Here are few ways I've considered addressing this:

  1. Ignore the test files similar to #20446. This is the least amount of work and will get other PRs passing and more likely to merge.
  2. Fix the eslint issues in the test files, add a grunt task or npm script (#20332) to transpile the test files, and update the references in index.html. This is obviously more work but would be more of a long term benefit.

I'm open to other ways to please @houndbot-ci when changing JS test files and willing to put in the work 😅

Assignee
Assign to
Time tracking