Add debug logging to see what environment variables are available

- Show all token-related environment variables
- Check specific variables: ACCESS_TOKEN, FORGEJO_TOKEN, GITHUB_TOKEN
- This will help diagnose why the secret isn't being detected
- Should reveal if it's a secret access issue or variable naming issue
This commit is contained in:
joe 2025-08-14 10:27:13 -07:00
parent 5e1b60b469
commit 9a21dceacf

View file

@ -392,6 +392,16 @@ jobs:
run: |
echo "Publishing .deb packages to Forgejo Debian Registry..."
# Debug: Show what environment variables are available
echo "🔍 Available environment variables:"
env | grep -i token || echo "No token variables found"
env | grep -i access || echo "No access variables found"
echo "🔍 Checking specific variables:"
echo "ACCESS_TOKEN: ${ACCESS_TOKEN:-'NOT SET'}"
echo "FORGEJO_TOKEN: ${FORGEJO_TOKEN:-'NOT SET'}"
echo "GITHUB_TOKEN: ${GITHUB_TOKEN:-'NOT SET'}"
echo ""
# .deb files are MANDATORY - fail if none exist
if ! ls *.deb >/dev/null 2>&1; then
echo "⚠️ No .deb files found in current directory"