simenandre / parse-sitemap

Parse sitemap to outputs in Github Action

parse-sitemap

Parse sitemap in Github Action

parse-sitemap's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): replace dependency faker with @faker-js/faker ^5.5.3
• chore(deps): update dependency dotenv to v16
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency eslint-config-prettier to v9
• chore(deps): update dependency eslint-plugin-jest to v28
• chore(deps): update dependency faker to v6
• chore(deps): update dependency husky to v9
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency ts-node to v10
• chore(deps): update dependency typescript to v5
• chore(deps): update dorny/paths-filter action to v3
• chore(deps): update googlecloudplatform/release-please-action action to v4
• chore(deps): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• chore(deps): update mshick/add-pr-comment action to v2
• chore(deps): update stefanzweifel/git-auto-commit-action action to v5
• chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• chore(deps): lock file maintenance
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency @actions/core to v1.9.1 [security]
• chore(deps): update dependency @vercel/ncc to ^0.38.0
• chore(deps): update dependency eslint to ~7.32.0
• chore(deps): update dependency eslint-config-prettier to ~8.10.0
• chore(deps): update dependency eslint-plugin-jest to ~24.7.0
• chore(deps): update googlecloudplatform/release-please-action action to v2.35
• chore(deps): update typescript-eslint monorepo to ~4.33.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• chore(deps): update actions/cache action to v4
• chore(deps): update dependency @types/node to v20
• chore(deps): update dependency dedent to v1
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/pull_request.yml

• actions/checkout v4
• dorny/paths-filter v2
• mshick/add-pr-comment v1

.github/workflows/push.yml

• actions/checkout v4
• actions/cache v2

.github/workflows/workflow.yml

• actions/checkout v4
• stefanzweifel/git-auto-commit-action v4
• GoogleCloudPlatform/release-please-action v2.28

npm

package.json

• @actions/core ^1.2.6
• sitemapper ^3.1.12
• @types/dedent ^0.7.0
• @types/dotenv ^8.2.0
• @types/jest ~26.0.23
• @types/node ~14
• @typescript-eslint/eslint-plugin ~4.23.0
• @typescript-eslint/parser ~4.22.0
• @vercel/ncc ^0.28.5
• dedent ^0.7.0
• dotenv ^9.0.2
• eslint ~7.26.0
• eslint-config-prettier ~8.3.0
• eslint-plugin-import ^2.22.1
• eslint-plugin-jest ~24.3.6
• faker ^5.5.3
• husky ^6.0.0
• jest ~26.6.3
• lint-staged ^11.0.0
• nock ^13.0.11
• prettier ^2.3.0
• rimraf ~3.0.2
• runtypes ^6.3.0
• ts-jest ~26.5.5
• ts-node ^9.1.1
• typescript ^4.0.5

---

• Check this box to trigger a request for Renovate to run again on this repository

Parse only matched (regex) urls?

In pulumi/docs#5783 I suggest using this GHA to parse Pulumi's sitemap. However, it's way too long. One of the options to solve this might be to split it up into pieces and run a matrix in GHA.

However, I realized today that maybe we rather want to match based on a regex? This way we can exclude testing things that are not really necessary to run Lighthouse on anyway.

E.g. Blog articles can be tested. But no API references.

re pulumi/docs#5783

The Checklist (was: Add README)

General

• Are the inputs and outputs defined in action.yml, where applicable?
• Are tests present, potentially leveraging Actions?
• Is the action published to GitHub Marketplace?

🗒 Documentation

• Is a README present with no typos?
• Are example workflow(s) in the README, ideally showing how the action can be used as part of a broader workflow?
• Are the prerequisites necessary in order for the example workflow to run included in README?
• Are inputs and outputs defined in README?
• Are Workflow status badges and / or third party badges present in README?

🤝 Open source

• Are CONTRIBUTING.md, CODE_OF_CONDUCT.md and other community health files present, like FUNDING.md, SECURITY.md, and SUPPORT.md?
• Are issue and pull request templates present?

📦 Release management

• Are semantically tagged releases regularly made available, potentially leveraging Actions?
• Are major / minor / patch tags kept up-to-date, potentially leveraging Actions?

🔁 Ongoing

• Keep the README up to date with changes
• Promptly respond to issues, discussions, and pull requests, potentially leveraging Actions
• Communicate future considerations or a feature roadmap, potentially leveraging GitHub project boards