Skip to content

Conversation

@farnabaz
Copy link
Member

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@gitguardian
Copy link

gitguardian bot commented May 27, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

πŸ”Ž Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
17467287 Triggered Generic Password b6d00a4 pnpm-lock.yaml View secret
πŸ›  Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


πŸ¦‰ GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented May 27, 2025

Deploying content with Β Cloudflare Pages Β Cloudflare Pages

Latest commit: 0c76010
Status:Β βœ…Β  Deploy successful!
Preview URL: https://88dd5e1f.content-f0q.pages.dev
Branch Preview URL: https://feat-copy-markdown.content-f0q.pages.dev

View logs

@pkg-pr-new
Copy link

pkg-pr-new bot commented May 28, 2025

npm i https://pkg.pr.new/@nuxt/content@3381

commit: 0c76010

@farnabaz
Copy link
Member Author

We use the /raw/[URL].md pattern to catch all routes that end with a .md file. Unfortunately, my attempts to support [URL].md were unsuccessful due to some limitations in route matching.

@farnabaz farnabaz marked this pull request as ready for review June 2, 2025 07:20
@farnabaz farnabaz merged commit 856f386 into main Jun 2, 2025
4 of 5 checks passed
@farnabaz farnabaz deleted the feat/copy-markdown branch June 2, 2025 14:06
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.

2 participants