-
-
Notifications
You must be signed in to change notification settings - Fork 13.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-generate PR description [G4F] #2336
Conversation
It seems like a good way to steal the secrets.GITHUB_TOKEN to your classmates accounts, |
It's alive! I was going to comment that you code as fast as a room full of Chinese hackers but then I saw your repertoire from 11 days ago https://github.com/yuri-val/auto-pr-description-action That's a thing G4F solved.... |
Yes, you are right. It's just a "free" rewrote to Python version of main action |
if I dont provide Rulles....
|
@yuri-val
|
You should also check repo Action permissions |
Your workflow looks mostly correct, but the permission issue (403: Resource not accessible by integration) could still arise if the default GitHub token lacks appropriate scope. Below are a few recommendations to troubleshoot and resolve the error:
The permissions you’ve set (pull-requests: write, issues: write) should generally be sufficient, but sometimes GitHub’s permission model requires more than expected. I recommend explicitly adding permissions for workflow runs and checking if it helps:
If you’re running this workflow in a forked repository or GitHub Actions environments where the default GITHUB_TOKEN might have limited permissions, using a PAT might be necessary. To generate a PAT: Update your workflow to use the PAT:
GitHub’s 403 errors can be tricky. Here are some additional steps for debugging:
This will allow you to understand whether the token has the correct permissions or is restricted. Summary of Changes
Here’s an updated version of your workflow incorporating these suggestions:
Let me know if this helps solve the issue, or if you need more support in adjusting the permissions. |
it brokes the app........... |
Bumping this pull request because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again. |
You need to do things like the copilot does to work properly. |
@hlohaus what do you mean? |
Hey, you need to run it on unit test workflow. |
@hlohaus I don't see the point of doing this for several reasons:
As a result:
|
I will merge your PR, but you will see. 🙅♂️ You have not enoght permission for writing to the Pull Request 🙅♂️ |
https://github.com/xtekky/gpt4free/actions/runs/11881376591/job/33105637066 RuntimeError: Failed to fetch branches. Exit code: 32768 |
Ok, I'll check it tomorrow. |
🎉 Feature Addition: Auto-generate Pull Request Descriptions! 🎉
This PR introduces a new GitHub Actions workflow that automatically generates descriptions for pull requests when they are opened or synchronized.
Key Changes:
.github/workflows/auto-pr-description.yml
yuri-val/auto-pr-description-g4f-action
to create informative PR descriptions automatically.Benefits:
Let's streamline our workflow and improve collaboration! 🚀