The same action can work normally in the personal fork, but not in the organizational repository. #121805
Replies: 2 comments
-
Oh,our organizational repository is https://github.com/PCL-Community/PCL2-1930 |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hello everyone, I am a member of @PCL-Community .I wanted to create GitHub Actions in one of our organization’s repositories through a pull request, so I created the GitHub Actions in the repository I forked. Later, this pull request was merged. The GitHub Actions I created work fine in my fork, but not in our organization’s repository. Sometimes it prompts ‘GitHub token not filled in’, but I am quite sure that I filled in the GitHub token correctly. I entered the token as a secret in the actions, and I have set the secret as my GitHub token in both our organization’s and my forked repository, and this token has all permissions. Why is this happening?
Beta Was this translation helpful? Give feedback.
All reactions