Minor doc update: github.token vs secrets.GITHUB_TOKEN

[DrEsteban]

docs/content/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/manage-caches.md

Line 79 in 8670647

GH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}

Since it looks like this example is using the built-in permissions model for the runner identity, I think this example should be github.token vs secrets.GITHUB_TOKEN. Since the latter implies the user must set up a secret beforehand with a personal access token.

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[ADAMSALAMA6667]

// Adam Pulse (ADMP) - Official Token Platform 💜 // Developed with love for decentralization and clarity

import React from "react"; import { Button } from "@/components/ui/button"; import { Card, CardContent } from "@/components/ui/card"; import { Input } from "@/components/ui/input"; import { motion } from "framer-motion";

const HomePage = () => { return (

<motion.h1 initial={{ opacity: 0, y: -20 }} animate={{ opacity: 1, y: 0 }} transition={{ duration: 0.7 }} className="text-4xl md:text-6xl font-bold text-pink-400" > Adam Pulse (ADMP) </motion.h1>

🚀 نبضك الرقمي في عالم لامركزي — اكتشف عملة ADMP، توكن المجتمع، NFTs، الحوكمة، والسيولة الذكية.

اشترِ الآن تتبع على Solscan اتصل بمحفظتك

[Sharra-writes]

Thanks for opening an issue! I'll look into this and get back to you.