Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

qase-tms / qase-javascript Public

Notifications You must be signed in to change notification settings
Fork 42
Star 49

Code
Issues 5
Pull requests
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

examples: update cucumber JS example #1476

Sign in to view logs

Sign in to view logs

examples: update cucumber JS example

examples: update cucumber JS example #1476

Summary
Jobs
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

12 warnings

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-node@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/env/env-type.ts#L13

Use an `interface` instead of a `type`

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/formatter/json-formatter.ts#L5

Use an `interface` instead of a `type`

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/formatter/jsonp-formatter.ts#L5

Use an `interface` instead of a `type`

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/models/attachment.ts#L1

Use an `interface` instead of a `type`

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/models/execution-sum.ts#L1

Use an `interface` instead of a `type`

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/models/host-data.ts#L1

Use an `interface` instead of a `type`

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/models/report.ts#L6

Use an `interface` instead of a `type`

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/models/report.ts#L12

Unexpected any. Specify a different type

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/models/short-result.ts#L1

Use an `interface` instead of a `type`

Run npm run lint -w qase-javascript-commons: qase-javascript-commons/src/models/stats.ts#L1

Use an `interface` instead of a `type`

Project qase-javascript-commons - Node 18

Project qase-javascript-commons - Node 18

succeeded May 24, 2024 in 1m 2s

Loading

Re-running jobs...

You can’t perform that action at this time.