Add debug logging to see what environment variables are available
Some checks failed
Comprehensive CI/CD Pipeline / Build and Test (push) Successful in 6m52s
Comprehensive CI/CD Pipeline / Security Audit (push) Failing after 6s
Comprehensive CI/CD Pipeline / Package Validation (push) Successful in 1m41s
Comprehensive CI/CD Pipeline / Status Report (push) Has been skipped
Some checks failed
Comprehensive CI/CD Pipeline / Build and Test (push) Successful in 6m52s
Comprehensive CI/CD Pipeline / Security Audit (push) Failing after 6s
Comprehensive CI/CD Pipeline / Package Validation (push) Successful in 1m41s
Comprehensive CI/CD Pipeline / Status Report (push) Has been skipped
- 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:
parent
08fecaf26b
commit
89b462b4d0
1 changed files with 10 additions and 0 deletions
|
|
@ -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"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue