You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: add comprehensive troubleshooting guidance for membership issues
Enhanced user experience for blocked users with detailed troubleshooting:
Action improvements:
- Clear step-by-step troubleshooting in action output
- Enhanced GitHub annotations with direct links
- Better error messages explaining membership requirements
Workflow improvements:
- Added comments explaining access requirements
- Troubleshooting guidance in workflow logs
- Clear instructions for making membership public
README improvements:
- Dedicated troubleshooting section
- Step-by-step resolution guide
- Common issues and solutions
- Links to GitHub organization people page
This addresses cases like blocked workflow runs by providing clear
guidance on verifying and fixing organization membership visibility.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
Copy file name to clipboardExpand all lines: .github/actions/security/org-membership-check/README.md
+27-2Lines changed: 27 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,10 +49,35 @@ The GitHub organization membership API works for both public and private members
49
49
50
50
This approach successfully detects all dotCMS organization members regardless of their membership visibility setting, using only the default GITHUB_TOKEN without requiring additional secrets or configuration.
51
51
52
+
## Troubleshooting
53
+
54
+
If you're a dotCMS team member but getting blocked by the security gate:
55
+
56
+
### Step 1: Verify Organization Membership
57
+
1. Visit: https://github.com/orgs/dotCMS/people
58
+
2. Look for your username in the member list
59
+
3. If you're not listed, you need to be added to the organization
60
+
61
+
### Step 2: Check Membership Visibility
62
+
If you are listed but still blocked:
63
+
1. Look for a "Make public" button next to your name
64
+
2. Click it to make your membership public
65
+
3. This allows the workflow to detect your membership
66
+
67
+
### Step 3: Contact Organization Owners
68
+
If you're not a member:
69
+
- Contact a dotCMS organization owner to be added
70
+
- Only organization members can trigger Claude workflows
71
+
72
+
### Common Issues
73
+
- **Private membership**: Most common cause - make membership public
74
+
- **Not a member**: Contact org owners to be added
75
+
- **Recent changes**: GitHub API may take a few minutes to reflect visibility changes
76
+
52
77
## Security Considerations
53
78
54
79
- Only checks membership in the dotCMS organization (hardcoded)
55
-
- Authorizes all organization members (both public and private)
80
+
- Authorizes organization members (requires public membership visibility)
56
81
- Logs authorization results without sensitive details
57
82
- Uses default GITHUB_TOKEN (no additional secrets required)
58
-
- No configuration or setup required for team members
83
+
- Provides clear troubleshooting guidance for blocked users
echo "::notice::Organization membership check result: $membership_result for ${{ inputs.username }}"
73
+
74
+
if [ "$membership_result" = "UNAUTHORIZED" ]; then
75
+
echo "::notice::❌ BLOCKED: ${{ inputs.username }} failed organization membership check. If you're a dotCMS team member, visit https://github.com/orgs/dotCMS/people and ensure your membership is PUBLIC."
76
+
else
77
+
echo "::notice::✅ AUTHORIZED: ${{ inputs.username }} is a dotCMS organization member"
0 commit comments