The agent session (with custom environment) fails when pushing its output to the GitHub repo #184244
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Update: it's actually a logic bug in my pipeline regarding to the access token for retrieving the Git submodules. I'd like to share more details here as a lesson learn for my own. My repo has a git submodule to contain another repo called c1. And the The logic bug is: the last step uses the token, which has no access to the current repo (only access to |
Beta Was this translation helpful? Give feedback.



Update: it's actually a logic bug in my pipeline regarding to the access token for retrieving the Git submodules.
I'd like to share more details here as a lesson learn for my own.
My repo has a git submodule to contain another repo called c1. And the
copilot-setup-steps.ymlis as follows