Skip to content

Change "insights" to "quarkus-insights" and remove tag of "quarkus" - #2832

Closed
insectengine wants to merge 17 commits into
quarkusio:mainfrom
insectengine:RemoveOrphanTags
Closed

Change "insights" to "quarkus-insights" and remove tag of "quarkus"#2832
insectengine wants to merge 17 commits into
quarkusio:mainfrom
insectengine:RemoveOrphanTags

Conversation

@insectengine

Copy link
Copy Markdown
Collaborator

For discoverability and clarity, I'm changing the "insights" tag to "quarkus-insights" on 17 posts. I'm also removing an orphan "quarkus" tag that doesn't need to exist.

** If you are updating a guide, please submit your pull request to the main repository: https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc **

…rkus"

For discoverability and clarity, I'm changing the "insights" tag to "quarkus-insights" on 17 posts. I'm also removing an orphan "quarkus" tag that doesn't need to exist.
@quarkus-bot

This comment has been minimized.

@holly-cummins

Copy link
Copy Markdown
Contributor

I was briefly puzzled by the failures in this PR, then I worked out what was happening. It looks like the checks of #2713, but #2713 isn't merged. And I didn't know why #2713 was finding non-fragment failures. I assumed it had accidentally fixed a bug in the crawler.

But no. It's that we happen to have blogs on the front page now (ie recent blogs) which expose the pre-existing tag problem fixed by #2831. This PR causes the link checker to run on the front page, which it wouldn't always, so it is failing with the issue.

@holly-cummins holly-cummins left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we wanted to be really fancy we'd add a redirect from /tags/insights to /tags/quarkus-insights, but I don't know if anything would ever have linked to the old url.

actions-user and others added 15 commits July 13, 2026 06:27
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Runs Lighthouse against the test server after smoke tests, scoring
performance, accessibility, best practices, and SEO for key pages.
Results appear as a color-coded table in the GitHub step summary and
are uploaded as build artifacts.

Uses npm ci with a lockfile to pin @lhci/cli dependencies.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

# Conflicts:
#	.github/workflows/build.yml
Keeps @lhci/cli and any future npm dependencies up to date.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Reuses the link_scope step outputs: skips when no HTML changed, tests
only changed pages (capped at 5) for partial PRs, and falls back to
key pages (/, /guides/, /blog/) for full checks. URLs are now passed
via CLI args instead of hardcoded in lighthouserc.js.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Reads report URLs from .lighthouseci/links.json (written by the
temporary-public-storage upload) and adds them to the step summary
table.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@quarkus-bot

This comment has been minimized.

@github-actions

github-actions Bot commented Jul 13, 2026

Copy link
Copy Markdown

🙈 The PR is closed and the preview is expired.

@quarkus-bot

quarkus-bot Bot commented Jul 13, 2026

Copy link
Copy Markdown

Status for workflow Build

This is the status report for running Build on commit 29f1d83.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@insectengine

Copy link
Copy Markdown
Collaborator Author

Was easier to just close this PR and redo the work and resubmit to avoid the unnecessary commits.

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.

3 participants